The challenge
Groove Life sold through multiple channels with different fulfillment paths. Its integration needed to preserve the distinction between e-commerce, wholesale and other order sources rather than send every order into the same shipping configuration.
The move into Microsoft Business Central introduced another challenge: the public API did not expose all of the business-specific shipping information required by fulfillment. The connection had to account for the customer’s customized environment.
The implementation
Preserve the channel-specific fulfillment rules
DataAutomation’s earlier Skubana integration mapped sales channels to ShipStation stores and used the client’s order labels to control when orders entered fulfillment.
Fill the gaps in the standard ERP API
For the Business Central connection, DataAutomation combined the public order API with the customer’s OData endpoints to obtain shipping-agent and service information. The workflow transformed those fields, mapped shipping methods, created orders in ShipStation in batches and updated the source system.
Build the handoff around the intended order flow
The integration preserved the operational meaning of source data where standard interfaces were incomplete. Fulfillment routing remained aligned with the scope and requirements of the intended order flows.
What changed
Groove Life increased sales by 35%, a result DataAutomation attributes to the connections built for the business. Channel-specific orders and the shipping information held in its customized ERP could move into fulfillment through the appropriate workflow.
This gave the business a path through a common enterprise integration problem: the standard API exposed only part of the information the downstream team needed. The missing shipping details became part of the workflow instead of a separate manual lookup.
The scope of the engagement
Custom integration where standard connectors cannot expose the fields needed by operations.
Business outcomes and timelines reported by DataAutomation.