Microsoft Dynamics GP and ShipStation integration

What moves between them

Sales orders from ShipStation flow into Microsoft Dynamics GP as receivables documents, with ShipStation customers mapped to existing GP customers and ShipStation line items mapped to GP inventory items. Shipment status from ShipStation updates back to Microsoft Dynamics GP so the financial system reflects what has shipped. Inventory levels are polled from both directions: ShipStation warehouse stock flows into GP inventory on demand, and GP inventory adjustments are read to update ShipStation warehouse counts. The integration runs on a schedule tied to order fulfillment cycles rather than waiting for push events.

How ml-connector handles it

ml-connector stores the Windows domain credentials securely and presents them to Microsoft Dynamics GP's on-premises SBA or SOAP endpoint over HTTPS. ShipStation API keys are stored encrypted and presented on each REST call with rate-limit backoff. Because neither system supports full bidirectional webhooks, ml-connector polls ShipStation's modifyDate filter for order and shipment changes, and polls Microsoft Dynamics GP with ModifiedDate filters on inventory and customer records. Orders map to GP documents by matching ShipStation customer username to GP customer ID and ShipStation SKU to GP item code. The integration handles the fact that Microsoft Dynamics GP's fiscal periods must be open to create transactions, and it tracks the status of orders through ShipStation's immutable states (shipped, cancelled). Each record carries a full audit trail so replays are possible if a downstream call fails.

A real-world example

A mid-sized e-commerce retailer runs Microsoft Dynamics GP on-premises for accounting and inventory, and uses ShipStation to manage order fulfillment across their website, Amazon, and eBay. Before the integration, fulfillment staff picked and packed orders in ShipStation, generated labels, and shipped packages, but the orders never reached the accounting system until the finance team manually entered them as sales invoices at month-end. With Microsoft Dynamics GP and ShipStation connected, each order flows into Microsoft Dynamics GP automatically with the correct customer and item mappings. When a shipment is marked as shipped in ShipStation, the status updates into the corresponding GP document. At month-end, the revenue is already booked, inventory has been updated in real time, and the finance team has visibility into what shipped versus what is still pending.

What you can do

• •Sync ShipStation orders into Microsoft Dynamics GP as sales documents with customer and item mapping.
• •Pull shipment status from ShipStation back into Microsoft Dynamics GP to reflect fulfillment progress.
• •Map ShipStation customers and SKUs to existing Microsoft Dynamics GP customers and inventory items.
• •Authenticate to on-premises Microsoft Dynamics GP via Windows Active Directory and to ShipStation via API keys.
• •Poll both systems on a schedule with retries, rate-limit backoff, and a full audit trail on every record.

Questions

How does the integration authenticate to on-premises Microsoft Dynamics GP?

ml-connector stores a Windows domain account securely and presents it to Microsoft Dynamics GP's SBA or SOAP endpoint using Negotiate/Kerberos or NTLM authentication. The domain account must be created by the customer and granted the appropriate user role in Microsoft Dynamics GP. The GP instance must be exposed through the customer's firewall with a valid SSL certificate or through a local agent.

Which direction do orders flow between the two systems?

Orders flow primarily from ShipStation into Microsoft Dynamics GP as sales documents. Shipment status updates flow back from ShipStation so Microsoft Dynamics GP's financial records reflect actual fulfillment. Inventory can flow in both directions: ShipStation warehouse stock updates Microsoft Dynamics GP inventory on demand, and GP inventory adjustments update ShipStation warehouse counts.

How does the integration handle ShipStation's immutable shipped status and Microsoft Dynamics GP's fiscal period constraints?

ml-connector respects ShipStation's immutable order states and does not attempt to modify orders after they are shipped or cancelled. For Microsoft Dynamics GP, it validates that the fiscal period is open before creating transactions, and it tracks when orders were created so it does not retry against closed periods. If a period closes before an order is posted, the integration surfaces the error with full audit context.