Treat a business system as “ship a few pages and tweak later” and the cycle dies in field edits. Walk it as engineering. Each stage has something you can sign: main path, state machine, migration list, pilot record, who closes the old road. A website has its own steps. A business system is about walking real documents on the floor. Cost and cycle depend on which phase you stop at. See cost and cycle.
List roles, documents, exceptions. The main path decides phase one: inventory, work orders, project, or after-sales. An unclear main path means rework later. Compare why spreadsheets and WeChat are not enough.
Who can change price, who can ship, what happens on a stockout — write configurable rules. Wholesale stringing, factory splits, dispatch close: pick the shape here. See inventory swimlane, split orders into work orders, dispatch close the loop.
How old sheets migrate, whether finance and courier connect — decide before build. Migration is in how to migrate old data, APIs are in connect finance?. Extend or rebuild is in extend or rebuild.
Walk real documents from order to cash. Not demo data. Accept on whether the work clock is the same window. See ledger or operations.
Name a system admin and an exception owner. Close formal intake in the group. Nobody-uses usually dies here. See nobody uses it after launch. If the floor is still messy, use the checklist. See how to diagnose.
The usual stall is not technology. Nobody inside can sign “may this order ship first and backfill later.” Sales wants speed, the warehouse wants accuracy, finance wants accounts. At kickoff name who supplies facts, who reviews rules, who orders the old road closed — two major change rounds max. More than two usually means the main path was never set. Packaged vs. custom belongs after G1, not after buying a suite and then inventing the work. See packaged vs. custom, ERP or custom.
DaXi delivers business systems through these gates, and can plan the website and mobile with the same team. Go to Business systems service page and send the current state, or call +86 139-2520-6166. How the path differs with and without a system is in how the work path differs. Project contracts take milestones through G2. See how to manage milestones.
Write the not-doing list at kickoff: no MRP in phase one, no ten-level approval, not every API. Shrink scope so document quality can rise. Changes are written. Verbal “add a module” thrashes the state machine. One week after launch, sample real outbound for a system order number — that beats a satisfaction survey. Collect master data by document with required fields and examples. Do not say “just send the sheets.” Do not cut over on a peak day. Put parallel-run days in the contract.
G4 pilot a slice of a real peak day, not weekend demo orders. If it fails, stay at G4. Do not force the planned cutover. G5 needs the owner in the room. An implementation consultant cannot close a WeChat group alone. Train by role. Warehouse and sales do not sit the same module tour. On launch day check that test orders do not mix into real reconciliation. That is engineering hygiene, not extra value. Walk all five gates and the system becomes daily work. Miss one and in three months you are back to “let’s use the sheet.”
Send the main path, the sheets you use, and the old road you will close. Engineering returns G1–G5 scope and acceptance so the project does not stall in a demo account.