Catalog, inventory, orders, customers, warehouse, finance, and reporting
Workflow
Define a first workflow you can verify
Begin with the work that creates the most avoidable effort: correcting product records, reconciling stock, handling order exceptions, or keeping a website current. Name the people who own the process and describe what a successful outcome would look like. For example, a retailer might choose a receipt-to-available-stock workflow. The acceptance check is not simply whether a receipt screen exists. The team needs to confirm the item, quantity, location, discrepancy handling, and the point at which stock becomes available for the next step.
Workflow
Prepare records before moving them
List the systems and files that hold products, customers, suppliers, inventory, and open work. Agree which source is authoritative for each record. Fix duplicate identifiers, inconsistent units, and missing required fields in a representative sample before considering a larger migration. Discuss what must be retained for historical reference and which records need to support active operations. Record counts alone are not an acceptance test: sample the values and relationships your team depends on.
- Assign an owner for each source and mapping decision.
- Separate product identity, physical stock, pricing, and channel content.
- Keep a correction log and agree how rejected records will be reviewed.
Workflow
Make integration boundaries explicit
A logo or a broad category name is not an integration specification. For each required connection, confirm the exact platform, account, supported data, direction of transfer, frequency, and error handling. Identify where approval is needed before a change becomes live. A website project, an order connection, and marketplace publishing can involve different responsibilities. Include those boundaries in the proposed implementation scope so your team knows what it will operate and what needs separate work.
Workflow
Rehearse the exceptions before launch
Choose representative scenarios with the people who will use the workflow. Include a normal case, a missing record, a stock discrepancy, a correction, and a role that should not be allowed to approve the action. Decide who signs off and what evidence they need. Agree on training, support contacts, the launch sequence, and a recovery plan before changing operational ownership. Timing and costs depend on the agreed modules, data quality, integrations, and scope; request a scoped proposal rather than assuming a fixed rollout duration.
- Write the expected result before running each scenario.
- Record unresolved gaps and ownership before launch.
- Expand to another workflow after the first one meets its agreed checks.
FAQ
Common Questions
Can we start with a few 1XA modules?
Yes. The public 1XA offering supports evaluating a few connected modules or a broader ERP rollout. The first scope should be agreed around your workflow, data, and integration requirements.
How long does a 1XA ERP implementation take?
There is no single timeline for every business. Ask the team for a scoped plan after reviewing your modules, source data, integrations, testing, and training needs.
Next step
Discuss your implementation scope
Tell us which records, channels, and handoffs need attention. We will focus the conversation on a practical starting point for your business.