IMPLEMENTATION
One incoming channel. One ERP. An agreed result.
A pilot starts with your actual order process. Pricing and delivery milestones follow scoping; the public demo is a reference, not a promise of a ready-made connector.
1. Workflow discovery
Map your order formats, monthly volume, customer identifiers, product catalogue, price agreements and stock rules. Identify which decisions should stay with your team. Use non-confidential samples for the initial conversation.
2. Written scope and quotation
Agree the input channel, ERP sandbox, deliverables, exclusions and acceptance criteria. Confirm price, payment milestones, delivery expectations and cancellation terms before commissioning work. No payment is collected by the enquiry form.
3. Sandbox implementation
Configure extraction, customer and SKU mapping, validation and review. ERP connectivity depends on available APIs, permissions and a suitable customer-provided test environment. Inbox access and additional channels are scoped separately.
4. Acceptance testing
Use an agreed sample set to check field accuracy, exception handling, duplicate submissions, permissions and recovery from failures. Compare manual effort against your baseline; no savings or accuracy percentage is promised in advance.
5. Handover and optional support
Provide the agreed workflow documentation and operating instructions. Production release requires acceptance and authorised access. Ongoing maintenance, monitoring, response times and further integrations are separately agreed.
Start with a scoped pilot.
Discuss your inputs, acceptance criteria and integration access before agreeing on delivery and price.
Discuss your order workflow →