BurtonSoftware01 Must we replace our current ERP?
Not necessarily. Burton can be evaluated for a warehouse or fulfillment workflow alongside existing systems. Feasibility depends on validated interfaces, clear data ownership, and agreed process responsibilities. Keeping a reliable finance or seller system while improving warehouse execution may be appropriate for some projects.
Define the system of record for customers, products, purchase orders, stock, orders, shipping results, and invoices. Avoid allowing two systems to update the same field without a reconciliation rule.
02 Can Burton connect to our software?
Channel, ERP, accounting, carrier, and EDI connections must be assessed individually. A name or logo in product material does not confirm that a connector supports your account, region, version, transaction types, or required fields. Confirm an existing supported connection or a scoped custom integration before planning rollout.
| Requirement | Details to confirm |
|---|---|
| Systems and authorization | Product/version, account and region, API access, scopes, and third-party approval. |
| Data flow | Orders, SKUs, inventory, tracking, ASN, invoices, or other agreed objects; direction and ownership. |
| Timing and volume | Webhook or polling, acceptable delay, peaks, rate limits, and batch sizes. |
| Mapping | Customer IDs, channel/internal SKUs, units, status codes, and required fields. |
| Failure handling | Duplicate prevention, retries, error queues, alerts, reconciliation, and a named support owner. |
| Acceptance | Representative data, partial shipments, canceled orders, expired access, and recovery checks. |
03 What about a custom API?
API availability alone does not prove compatibility. Review documentation and sample data, validate authentication and mapping, and test both normal and failed requests. Include expected business behavior when a connection is unavailable. Custom development, maintenance, and external service fees belong in the project scope.
04 What should we keep, integrate, or replace?
Keep processes that already work reliably. Integrate when a clear handoff can improve visibility without duplicating control. Replace a process only when the proposed workflow meets acceptance criteria and the transition plan is agreed. A limited pilot can test one unresolved handoff before a wider change.
See customer API and channel documentation and custom integration services.