Industry Solutions

BigLedger’s customers are, first, multi-branch Malaysian consumer-electronics retailers — several companies in one group, a couple of dozen branches, an online arm and a distribution arm — and, after them, pharmacy chains, automotive service groups, precision manufacturers and franchise-model F&B. That first shape is the wiki’s running example, GadgetSphere Sdn Bhd, and every module page is written around it. The other shapes are not separate editions and do not get separate pages: BigLedger is one product, and what differs by sector is which applets you lean on and one or two behaviours worth knowing before go-live. Those appear as examples and callouts inside the page whose fact they vary. The six per-industry pages this section used to hold were folded into those pages on 2026-09-16.

Where each industry’s specifics live

Multi-branch retail, online and distribution (the running example)

• The counter, and the price a till rings up by branch and by role — POS module and its use case
• The B2B order desk, stock at a customer’s site, and orders that arrive from a marketplace or the storefront — Sales module use cases
• Marketplace links and the storefront itself — E-commerce module

Wholesale and distribution

• One invoice a month for a customer who takes weekly deliveries — Sales use case 1
• Long-term supplier agreements, consignment from a brand principal, and giving a supplier a window — Purchasing module and its use cases
• Your stock on somebody else’s shelf, and theirs on yours — Inventory use case 5
• What credit control really does (a scheduled job, not a save-time block) — Best practices

Pharmacy chains and food and beverage

• The counter — POS module
• Perishables on batch tracking with expiry dates, portioning and re-packing with Stock Conversion (and which way its tabs read), two-step transfers from a central kitchen — Inventory module and its use cases
• Which receiving document books the stock — the receiving-pair callout on the Purchasing module

Automotive service groups

• The consultation, its inspection checklists, the job sheet, and the fact that only the sales invoice bills and moves parts — Sales module, then the Car Workshop applet
• Serialised parts, and extended warranties as an item type — Choosing an item type; the warranty review queue is the Warranty Admin applet
• Getting parts in — Purchasing overview

Precision manufacturing and assembly

• Process templates, job orders, work logs, what finalisation moves and at what value, and what the module has no engine for — Manufacturing module and its use cases

Professional services and projects

• The job sheet records, the sales invoice bills — Sales module
• Expense claims, the one approval engine with delegation, and sampling — Claims module
• Budget control through votebooks, and planned billing and collection — Financial Accounting module

What is true whatever you sell

One data core per tenant, so there is nothing to integrate between the applets. One document in each chain posts — the sales invoice or the POS cash bill on the way out, the purchase invoice (or GRN Stock In) on the way in — and everything else is a record. Companies, branches and locations underneath, with default GL codes per company, cashbook access per branch and stock balances per location. And Malaysian compliance built in, so item-level e-Invoice classification matters from day one. Start with the platform overview and the modules.