|

Shopify Led Fulfillment: Configuring Dynamics 365 Business Central for eCommerce-First Workflows

Shopify Led Fulfillment is often the preferred workflow for direct-to-consumer brands that perfected their logistics on the frontend long before upgrading to a comprehensive ERP like Business Central. A recent discussion on the Dynamics 365 Community forums highlighted a scenario many businesses face: they want to keep using their existing Shopify shipping apps (like ShipStation or Shippo connected directly to the store) while simply treating Business Central (BC) as the financial backend.

Usually, Microsoft’s native connector assumes the ERP is the “boss” of inventory. It expects the warehouse team to pick, pack, and post the shipment in BC, which then tells Shopify, “Hey, we shipped this.” But what happens when you want to flip the script?

The Challenge: Making Business Central a “Passive” Receiver

In the forum discussion, a user outlined a specific requirement: they want orders to be fulfilled within Shopify, with that status update subsequently flowing into Business Central. They don’t want to log into the ERP to click “Post Shipment” for every sneaker or t-shirt sold.

Standard configurations in the Shopify Connector usually create a Sales Order in BC when a customer buys something. If the fulfillment happens in Shopify after that order is created in BC, you can run into a synchronization gap. BC sits there waiting for you to tell it the goods are gone, while Shopify already knows they are.

Configuring the Connector for Shopify-Led Flows

To achieve Shopify Led Fulfillment, you need to adjust how the connector handles order synchronization. While the native connector is robust, it favors a “BC-first” fulfillment logic. However, you can manage this by focusing on the Order Handling settings in the Shopify Shop Card.

  1. Order Import Triggers: Ensure your sync runs frequently. If an order is fulfilled in Shopify before it even hits BC (common with immediate auto-fulfillment apps), the connector needs to know how to handle a “Closed” or “Archived” order.
  2. Auto-Create Sales Orders: You will still likely want to create Sales Orders to reserve inventory (even if momentarily).
  3. The Fulfillment Sync: The crucial part is usually the “Sync Shipments to Shopify” toggle. If you are doing Shopify-led fulfillment, you generally want to ensure BC isn’t trying to overwrite Shopify’s data.

Note: For a truly automated flow where a Shopify fulfillment auto-posts the shipment in BC, customization or Power Automate flows are often required to bridge the gap between the “Fulfillment Status” field on the Shopify Order and the “Post Shipment” action in BC.

The Migration Strategy: Flipping the Data Flow

The forum user also brought up an interesting migration strategy that deserves a closer look: Can you start by pushing items from Shopify to BC, and then later reverse it?

The short answer is yes, but it is dangerous if you aren’t careful.

Phase 1: Shopify to Business Central (Initial Setup)

Many companies start with a blank BC environment. They use the connector’s “Sync Items from Shopify” feature to populate the ERP.

  • Why do this? It saves manual entry.
  • The Config: You set the sync direction to From Shopify. You must configure Item Templates in BC so that when a new product is created, it knows the correct Gen. Prod. Posting Group and Inventory Posting Group.

Phase 2: The Switch (Business Central to Shopify)

Once the items exist in both systems, the goal is to make Business Central the master of data (price and inventory).

To do this successfully:

  1. Stop the Sync: Pause the connector.
  2. Match the SKUs: Ensure the Variant Codes and SKUs in BC match the Shopify SKUs exactly. The connector relies on this link.
  3. Reverse Direction: Change the sync setting to To Shopify.

Warning: When you flip this switch, BC becomes the source of truth. If your inventory counts in BC are zero (because you haven’t done a stocktake yet) and you sync, you will wipe out the inventory availability on your live website. Always ensure your Physical Inventory Journal is posted and accurate before reversing the sync direction.

Why This Matters

Allowing for Shopify Led Fulfillment reduces the friction for warehouse teams that are used to the simplicity of eCommerce interfaces. While Dynamics 365 Business Central offers superior financial controls, forcing a retail team to learn a complex warehouse module on Day 1 can kill adoption.

By carefully configuring the connector and planning a phased item migration, you can have the best of both worlds: the agility of Shopify fulfillment and the financial rigor of Microsoft Dynamics.

Similar Posts