Skip to content

Every case has its cost. Every sale, its margin.

Distribution MA’s ERP, for a Montreal food distributor, designed and built by Witify. It costs every case, shows the margin before the sale and sends every document to QuickBooks.

Client
Sector
Food distribution
Technologies
Laravel, Vue, QuickBooks

01 The numbers

Four numbers, and where they come from

Two results measured by Distribution MA, two rules of the system.

  • +35%

    margin The real cost of every case is known when the price is set.

  • −55%

    manual order entry Restaurants place their own orders on the portal.

  • 8

    kinds of documents sent to QuickBooks Clients, suppliers, invoices, purchase orders, payments in and out, credit notes on both sides.

  • 3

    margin colours on every order line Green at or above target, orange below it, red at a loss.

The first two numbers were measured by Distribution MA after go-live. The other two are rules of the system.

02 Before

Prices that move, a spreadsheet that does not

Orders came in by phone and email, and the sales team typed them into the old system. Costs lived in an Excel workbook, updated when someone remembered, while supplier prices changed from one shipment to the next. The books were already in QuickBooks, so everything was keyed in twice.

Fig. 01 The inventory list before the ERP: one cost per product, whatever the shipment

03 One order

From the restaurant’s cart to the invoice in QuickBooks

Let us follow order C-B12 from a bistro, from the date picked on the portal to the invoice that lands in QuickBooks.

01 The portal

The restaurant orders and picks its day

The client sees its own prices and fills its cart. It picks a delivery day among the ones allowed for it. After 2:15 PM, the next day is no longer offered: the warehouse has time to prepare.
Fig. 02 The client portal cart, with the delivery date picker

02 The margin

Every line shows its margin before delivery

The office approves the order. Each line shows its expected margin, worked out from the item’s FIFO cost: green at or above target, orange below it, red at a loss. Here, the gloves are selling below cost.
Fig. 03 An accepted order, line by line, with the margin of each

03 The delivery

Confirm what actually arrived

When the truck comes back, each line is confirmed as delivered, forgotten or broken. A broken case leaves the inventory, a forgotten one stays, and the missing quantity is kept on record for the client.
Fig. 04 The delivery confirmation, line by line

04 QuickBooks

The completed order goes to QuickBooks on its own

As soon as the order moves to Completed, the invoice is created in QuickBooks with the quantities actually delivered. If the restaurant does not exist there yet, it is created first. The QuickBooks tab shows where the send stands, and the log keeps every attempt.
Fig. 05 The order’s QuickBooks tab, after the send

04 QuickBooks

QuickBooks stays the books, the ERP feeds it

Clients, suppliers, invoices, purchase orders, payments and credit notes reach QuickBooks at the right moment. Whatever is stuck shows up on the dashboard.

Dashboard

A rejected send does not go unnoticed

Each kind of document has its box: green when everything went through, red with the number of records to fix.

Log

QuickBooks’ message, word for word

The record says why the send failed. Once fixed, one button runs the sync again.

05 FIFO cost

A case costs what its shipment cost

Each receipt joins a queue with its own cost. Sales use up the shipments in order: the FIFO cost is the cost of the current lot. The high and low costs of the lots still waiting show what comes next, and the recommended price is recalculated with the cost, from the target margin.

Fig. 06 An item record: its shipments and their cost, and the margin that follows

06 Our choices

Three choices so the margin shows before the sale

Three decisions mattered more than the others. For each one: the risk to avoid, what we chose, and what the client gains.

  1. QuickBooks keeps the books.

    The risk
    Replacing the accounting tool, or keying everything into two systems that end up disagreeing.
    Our choice
    The ERP itself creates clients, suppliers, invoices, purchase orders, payments and credit notes in QuickBooks, and logs every send.
    The gain
    Accounting keeps QuickBooks, with no double entry, and sees at once what did not go through.
  2. Cost follows the shipment, not an average.

    The risk
    An average cost, or a cost written once in a spreadsheet, hides supplier increases until the margin is gone.
    Our choice
    Each receipt keeps its cost in a queue, first in, first out. Margin targets are set per item and can differ for a client.
    The gain
    The salesperson sees the real margin on every line before accepting the order.
  3. A delivery is confirmed line by line.

    The risk
    Invoicing what was ordered rather than what arrived, and letting the inventory drift with every broken case.
    Our choice
    When the truck comes back, each line is confirmed as delivered, forgotten or broken. The invoice then goes out with the delivered quantities.
    The gain
    A correct invoice the first time, and an inventory that matches the warehouse.

07 Under the hood

What the system is made of

A web application built for Distribution MA, connected to its accounting.

Application
Laravel, Vue, TypeScript, PHP, Tailwind
Data
MySQL, Redis, Horizon queues
Accounting
QuickBooks Online API, OAuth connection, token renewed automatically, taxes and clients imported at the start
Portal
Client portal and public site, per-client prices, exclusive products, card payments
Quality
258 automated tests, static analysis

Does your margin melt between two shipments?

Thirty minutes to follow one of your orders, from cart to QuickBooks.

Or write to us
Next case study Original Garage Motosport Read the case study

Names and figures shown in the interfaces are examples.