Frequently asked questions
Got questions? We’ve answered the most common ones here.
What if the integration creates bad data in our ERP?
We build and test in sandbox environments before touching production. All integrations include validation rules that catch malformed data before it syncs. We also implement logging and alerting so if something unexpected happens, we know immediately and can intervene before it spreads.
How long does an ERP integration take?
It depends on your ERP, the complexity of your data, and how customized your implementation is. Simple integrations with standard configurations typically take 6–8 weeks. Complex projects with custom logic, multiple data flows, and legacy systems can run 12–16 weeks. We scope your specific situation before committing to a timeline.
Who from our team needs to be involved?
We need access to someone who understands your ERP configuration—typically your ERP admin, IT lead, or the consultant who implemented it. We also need input from operations on how orders and inventory actually flow. Expect a few hours per week during discovery and testing phases.
What happens when something breaks after launch?
Integrations include monitoring and alerting from day one. We provide a post-launch support period to address any issues that emerge with real transaction volume. For ongoing support, we offer retainers that include monitoring, maintenance, and quick response when problems occur. We also document everything so your team or another partner can take over if needed.