Most shop projects in wholesale do not stall on design or on features. They stall in the weeks when two teams try to find out how the ERP really works. Which field holds the dealer price? What happens when an order export fails at night? Who knows?
That is why the first thing we ask for is the complete documentation of your ERP interface. After that, the integration work is ours. 8 connectors are already built, including SAP, Microsoft Dynamics, Priority, Salesforce, and the ERP stays the leading system for prices, stock and article numbers.
What complete means
- Access: how a system authenticates, which environments exist (test and live) and which limits apply
- Master data: articles, dealers and accounts, with the fields and their meaning
- Commercial data: dealer prices, special prices, promotions, bundles, terms
- Availability: stock per warehouse, and how current the values are
- Flows back: orders, call-offs, new dealer registrations
- Documents: delivery notes and invoices
- Errors: codes, messages and what each means for an order
What flows where
From the ERP to the shop come products, dealers and accounts, including open items, cheques and revenue targets, special prices, promotions and bundles, delivery options and documents. From the shop back to the ERP go orders and call-offs, automatically. New dealers register in the shop, your team creates the customer in the ERP, and the account is picked up from there.
Three questions to settle early
One dealer, one number
Does every dealer have exactly one customer number, and are price agreements tied to it?
Who gets the alert
Who in your team is told at once when an interface or an order export fails?
Who answers questions
Which person knows the interface and has time for questions during the integration?
If the documentation is not complete
That is normal, and it is not a reason to rule a project out. A more complex ERP means more effort on our side, not more effort on yours. What helps most is honesty about the gaps: a list of what is missing is worth more than a document that looks complete and is two versions old.
After go-live
Integration does not end with the first order. Interfaces fail, exports get stuck, a field changes meaning after an ERP update. Your team is told at once when an interface or an order export fails, so a problem is solved before a dealer notices it. Transitions with manual imports are possible while an interface is being built.
See TireCloud.One in action
Talk to us about your business. We show you the platform and answer your questions.