Industry Solutions
You run shops, a distributor, a pharmacy or F&B group, a workshop, a factory floor or a firm that bills for time, and want to know which parts of BigLedger you lean on. There is no sector edition or mode: every business gets the same applets, posting chain and master data. What differs comes down to four decisions, and this page routes each kind of business to the module pages that carry the detail. BigLedger’s customers are, first, multi-branch Malaysian consumer-electronics retailers (the running example, GadgetSphere Sdn Bhd), then pharmacy chains, automotive service groups, precision manufacturers and franchise-model F&B.
The four decisions that differ by sector
- Which document in your chain posts. Only one per chain: the POS cash bill or the sales invoice on the way out, the purchase invoice or the GRN Stock In on the way in. Quotations, orders, job sheets, consultations, blanket agreements and job orders are records that move nothing (Practice 1).
- What your items are tracked by — quantity, serial, batch with expiry, or not stock at all — fixed once the item has history (Choosing an item type).
- Where stock sits that is not your own shelf — a partner’s showroom, a customer’s site, a principal’s units on yours, a lorry between kitchen and outlet — each a different document, and only two of them post a journal.
- Which clocks nobody switches on for you — the credit-control sweep and the marketplace pulls run only where somebody created a clock (what runs when nobody presses a button).
Everything else is the same for every sector, including a group of companies — one tenant, intercompany pairing, a Default GL Codes tab that starts empty per company: start with Setting up a group.
Pick your business
Multi-branch retail, with an online arm
The cash bill takes the payment, the stock and the sale in one document, at a price three settings decide; handsets go on serials; walk-ins are reported monthly under one General Public buyer; and a marketplace order arrives numbered and FINAL, while the sales invoice raised from it moves the stock. POS module and its use case · Serial numbers · Sales use cases · E-commerce module · Consolidated e-invoice · Membership module
Wholesale and distribution
Blanket purchase orders, consignee stock transfers (quantity only), the Consignment Billing applet that is the principal’s bill to you, SO Consolidation (a sales agent on every order), and credit control that is an optional screen check counting one company plus a blacklist sweep that ships unscheduled and clears every flag before it re-flags. Purchasing module and its use cases · Inventory use case 5 · Sales use case 1 · Deciding on credit · Stopping a customer · Practice 3
Pharmacy chains, food and beverage
Batch tracking with expiry captured on the receiving line; portioning on Stock Conversion, whose Input is into stock and whose posting run was found not connected on 2026-10-06; the two-step stock transfer for kitchen to outlet; and one receiving pair per company. Inventory module, use cases 1 and 4 · Stock transfer guide · Purchasing module · POS module
Automotive service groups
The consultation is a case that posts nothing; the sales and purchase invoices raised from its tabs move money and parts. A warranty you sell is a Warranty item type; one you register is a support review queue. Sales module · Car Workshop applet · Choosing an item type · Warranty Admin applet · Purchasing overview
Precision manufacturing and assembly
Production is recorded, not planned or costed: only the supervisor’s finalisation moves stock, at each item’s own unit cost there (zero if never costed), and nothing posts a journal or runs a plan. Manufacturing module and its use cases · Reset MA on the Stock Adjustment applet
Professional services and projects
The job sheet records and the sales invoice bills. The claims engagement route takes approvers from the engagement’s roles, with a billing side and a markup ratio nothing applies, and its approval engine is the only one with delegation; Budgetary registers are consumed only by FINAL invoices, with no server-side budget check; Cashflow Projection figures are typed in. Claims module and use case 3 · Financial Accounting module · Sales module
What goes wrong, by sector
| What you see | Read |
|---|---|
| Goods counted twice after a delivery | The receiving-pair callout on the Purchasing module |
| A customer well over their limit keeps ordering, or a hand-set blacklist disappears | Deciding on credit, Stopping a customer |
| Finished goods at zero cost and no manufacturing journal | Manufacturing module — by design; Reset MA and a manual journal |
| A marketplace order with no running number | EcomSync Related Applets — a failed run, not a queue |
| The second company’s first invoice has a journal, and the debtor is short | The mapping that decides whether anything posts |
How you know you picked the right pages
In a test company: finalise one record and one posting document in your chain — only the posting document’s TraceDocument tab has a journal, and Stock Balance moves once, at its FINAL — then name the owner of each clock your sector depends on and read its Last Run Date in the Scheduler. The industry codes BigLedger holds — the MSIC code on the e-invoice supplier block, the industry on a CRM organisation — describe a party, and no sales, purchase, stock or journal process reads them.