- Current entities, stores, stock locations and the owners of each intended order or payment connection.
- Product, variant, barcode and unit mappings, with approved selling prices, supplier terms and cost definitions.
- Customer and order-recipient rules, including the evidence needed to attribute an anonymous purchase or its refund.
- Open orders, accepted supply, stock, assembly work, shipments, returns and financial balances with their original identifiers.
- Collection, payout, fee, refund and reversal history, including uncertain or disputed outcomes still needing reconciliation.
- Approval, tax, currency, access and account policies, together with representative normal and exception cases.
Implementation
Plan a rollout around orders, stock and the money behind each sale.
Start with representative store and online orders, then follow the goods and money through fulfillment, invoicing and returns. Agree the operating scope, responsibilities and acceptance evidence before configuring the application. Implementation is separate from platform usage pricing and depends on the records, rules and connections involved.
Implementation phases
Phase 1 · Team and ERP.ai
Define the retail operating model
Confirm legal entities, stores, sales sources, stock locations, product and variant identities, units and customer handling. Agree order, invoice, stock and production approvals. Identify actual cash, bank and processor collection evidence, fees, payouts and refund responsibilities, including money received before an order is approved.
Phase 2 · Team and ERP.ai
Configure a connected pilot
Set up approved products, prices, tax and currency rules, stock controls, posting accounts and the relevant assembly recipes and operations. Exercise store handover, pickup and shipment with shared reservations. Test accepted discounts, partial supply, held stock, payment uncertainty, fees, returns, credits and separately approved replacements.
Phase 3 · Team and ERP.ai
Reconcile the opening position
Map current stock and costs, open purchasing, work in progress, accepted orders, earlier fulfillment, invoices, cash and payment clearing. Preserve source identities, partial allocations, refund reservations and historical provider outcomes. Reconcile one opening ledger with nonposting detail so imported history cannot create fresh stock, invoices or money movement.
Phase 4 · Team and ERP.ai
Verify and enable the first scope
Confirm access, independent decisions, quantity and financial reconciliations, and failure handling with the responsible teams. Train users, approve the cutoff and opening position, then enable eligible new work. Expand to additional stores or sources after reviewing the first scope's results and resolving remaining exceptions.
| Role | Screens |
|---|---|
| Sales Associate | 2 |
| Sales Manager | 4 |
| Purchasing Manager | 2 |
| Fulfillment Operator | 5 |
| Warehouse Manager | 8 |
| Production Manager | 3 |
| Production Operator | 1 |
| Accountant | 3 |
| Finance Manager | 7 |
Role permissionsRoles and permissions →
Review product, pricing, commercial, stock, payment and access changes with the applicable owners. Preserve accepted orders, actual collections, shipped goods and posted history while applying approved amendments to eligible remaining work. Recheck mappings, reports, connections and training before expanding a channel or payment path. Verify the configured application’s behavior before launch; a proposed provider connection or website page is not evidence that the integration is installed.
1
Say what you need"Add a second approval above 10,000." Plain language.
2
Review the branchThe change lands on a branch with the diff and a test run.
3
ReleaseMerged into your workspace. Every user gets it.