Skip to main content
Batchlane is built around one idea: every operational action should leave a connected record. When the records stay connected, teams can answer inventory, QA, customer, and finance questions without rebuilding history in spreadsheets.

The source-record chain

  1. Settings and roles define workspace rules: locations, units, roles, team access, and production signoff policy.
  2. Address book stores customers and suppliers.
  3. CSV imports can seed items, lots, recipes, orders, customers, suppliers, and addresses.
  4. Receiving creates supplier lots and receive movements.
  5. Inventory holds the current lot ledger and movement history.
  6. Recipes define what production should consume and produce.
  7. Production consumes input lots, records actuals, creates output lots, and signs the batch record.
  8. Orders reserve and ship finished lots to customers.
  9. Documents and QA attach COAs, batch attachments, supplier files, export evidence, and audit files to the source record they support.
  10. Traceability, Reports, and QuickBooks handoff summarize the source records.

The ledger rule

Inventory quantity should change through movements, not silent edits. Receive, consume, produce, ship, adjust, transfer, correct, return, and scrap events create movement history. This lets Reports, Traceability, and QuickBooks handoff explain why a balance changed.

The document rule

Documents are not a folder system. A COA belongs to a lot, a batch attachment belongs to a run, and a generated export belongs to the export or report that produced it. If a document is missing or rejected, the work appears in Documents and QA and often on the Today dashboard.

The status rule

Statuses control what can happen next.
  • A held, quarantined, consumed, shipped, scrapped, or returned lot should not behave like available inventory. See Inventory.
  • A draft or archived recipe should not be scheduled for live production. See Recipes.
  • A completed or signed-off production run should preserve its history. See Production.
  • A shipped or canceled order should not be edited like a draft. See Orders.
  • A retired document should not be reviewed until it is restored. See Documents and QA.

Where to troubleshoot