Your first week in Lumen, day by day

Most failed rollouts fail in the same way: everything is switched on at once, nobody knows what is authoritative, and within a fortnight people are back in the old spreadsheet. Here is a calmer order.

Day 1 — the space and the shape of it

Create your space, set the currency and display settings, and switch on only the modules you will genuinely use this month. A café might start with POS, Catalog, Kitchen and Inventory; a distributor with Sales, Purchases, Inventory and Ledgers. Everything else can be turned on later without any migration.

Day 2 — the lists everything else hangs off

Import customers, vendors and items. Get the item list right before anything else: units, purchase and sale prices, reorder levels, tax treatment. Every invoice, purchase and stock count you will ever make points back at these records, and fixing them later means fixing history too.

Day 3 — opening balances

Pick a cut-off date — the first of a month is easiest — and enter what is true on that morning: customer receivables, vendor payables, stock on hand, bank and cash balances. Older detail stays in the old system. Resist the urge to backfill a year of transactions; nobody ever reads them.

Day 4 — people and permissions

Invite your team and grant access per module and sub-module: view, create, edit, delete. Give the smallest set that lets each person do their job, and decide now whether members should see profit figures — owners can hide them entirely. Every change anyone makes lands in the owner-only audit log.

Day 5 — run one real day

Do a full day of real work in Lumen: bill actual customers, receive actual stock, record actual payments. Keep the old process running in parallel for that single day and compare the two at close. You are looking for gaps in your setup, not bugs.

Week 2 — the second layer

Now add what makes the system pay for itself: reorder levels and low-stock alerts, proposals and e-signature for anything you quote, ordering links for customers or salesmen, and Ask Lumen for the questions you used to build reports for. Switch on payroll before the month ends, not during the last week of it.

Two rules that save rollouts

• One authoritative place, from day one. The moment a number lives in both Lumen and a spreadsheet, it lives in neither.
• Train on your own data. Generic training is forgotten by Friday. Walk your team through their actual customers and their actual items — that is what the training add-on is for.