Dynamics 365 Commerce: E-Commerce & Retail Channels Configuration

Commerce Architecture Overview

Dynamics 365 Commerce consists of three core layers:

• Commerce Headquarters – Central management console (runs on F&O environment). Defines products, catalogs, prices, discounts, channels, stores, POS registers, and payment methods. Acts as the single source of truth.
• Commerce Scale Unit (CSU) – Real-time processing layer (cloud-hosted or on-premises). Handles live operations: POS sync, shopping cart, checkout, inventory queries, and price lookup. The CSU caches frequently accessed data (products, prices, inventory) for sub-second latency.
• POS & Channel Apps – Client-side applications. Retail POS (desktop), MPOS (mobile), online e-commerce storefront (React), and third-party frontends communicate with the CSU or headquarters APIs.

Data flows from headquarters to the CSU via CDX (Commerce Data Exchange) jobs. Most operational queries hit the CSU for speed; master data changes (product, pricing, catalog) sync down periodically or on-demand.

Channel Types & Setup

Commerce supports four primary channel types:

1. Online Store Channel

• E-commerce website or mobile app.
• Configured with a domain, default currency, and payment methods (credit card, digital wallet, buy-now-pay-later).
• Linked to one or more fulfillment warehouses; orders can ship or be picked up in-store.
• Example: mystore.com hosted on Azure CDN with React storefront querying the Commerce OData API.

2. Retail Store Channel

• Physical brick-and-mortar locations with POS terminals.
• Each store is linked to a warehouse for inventory visibility.
• POS registers authenticate to the store, process payments locally, and sync transactions back to headquarters.
• Inventory is managed per store; transfers between stores trigger purchase orders or inventory movements.

3. Call Center Channel

• Voice-based sales through customer service representatives.
• Uses a web-based call center POS; CSR enters customer details, searches products, and creates an order.
• Supports customer-specific pricing (negotiated rates), special promotions, and notes (e.g., “VIP customer, 10% loyalty discount”).
• Orders route to fulfillment like any other channel.

4. B2B or Marketplace Channel

• Third-party integrations (Shopify, Amazon, eBay, or custom APIs).
• Products and orders sync via connectors; F&O serves as the back-office system.

Product Catalogs & Attributes

A product master in F&O contains core data (name, SKU, unit, dimensions, weight). To expose a product in a specific channel, you add it to a catalog.

Catalog Setup:

• Product Master – Defines core product attributes (name, SKU, unit of measure, dimensions, barcode).
• Channel-Specific Attributes – Commerce allows channel-specific product details: display name, description, images, SEO keywords, and category assignments per channel. The same SKU might be called “T-Shirt (Blue)” online but “Tee - Blue” in POS.
• Catalog Hierarchy – Organize products into categories (Men → Shirts → Casual). Each channel has its own category hierarchy; the same product can be in different categories per channel.
• Variant Dimensions – Size, color, style. Commerce groups variants under a master product (e.g., “T-Shirt” master with Size [S, M, L, XL] and Color [Blue, Red]). Each variant has its own SKU, barcode, and inventory.

Best Practice: Define product attributes at headquarters once, then clone or override them per channel to minimize maintenance.

Pricing & Promotions by Channel

Pricing in Commerce is hierarchical and channel-aware:

Price Hierarchy (evaluated in order):

1. Customer-specific price (negotiated rate for that customer in that channel).
2. Channel-specific price (price group linked to the channel).
3. Base product price (in the product master).
4. If no price is found, the product cannot be sold in that channel.

Promotions & Discounts:

• Channel-wide promotions – e.g., “Online: 20% off socks in July”.
• Cross-channel promotions – e.g., “All channels: Buy 2 shirts, get 1 free.”
• Time-based rules – Promotions activate on specific dates; useful for seasonal sales or flash events.
• Quantity thresholds – e.g., “Spend $100 online, get $20 off next order” (loyalty).

Retail POS & Store Operations

The Commerce POS runs on either desktop or mobile (MPOS). Key features:

• Product Lookup – Barcode scan or manual search; POS displays price, inventory, and promotions from the CSU cache.
• Cart & Checkout – Cashier adds items, applies discounts, collects payment (card, cash, gift card, loyalty points).
• Offline Mode – If CSU is unavailable, POS queues transactions locally and syncs when connection is restored.
• Store Operations – Inventory transfer, stock count, price override (with approval), customer lookup, loyalty enrollment.
• Receipt & Email – Print receipt or email to customer; integrates with email marketing tools.

Call Center Channel

The call center channel uses a web-based POS for CSRs (customer service representatives):

• CSR searches for customer by phone, email, or ID; recalls purchase history and loyalty balance.
• CSR browses product catalog on-screen and adds items to order.
• CSR applies manual discounts (authorized by manager) or loyalty redemption.
• Payment is collected by phone (PCI-compliant tokenization) or prepaid.
• Order is created and routed to fulfillment center; tracking sent to customer.

Shopify & Third-Party Integrations

Dynamics 365 Commerce provides native connectors for popular marketplaces:

Shopify Integration:

• Product Sync – Export F&O product master (SKU, name, description, variants) to Shopify. Shopify displays products on your Shopify store.
• Inventory Sync – Inventory quantities update bidirectionally. When online customer purchases, Shopify inventory decrements; F&O reserved-for-sales quantity increases.
• Order Sync – Shopify orders flow into F&O as sales orders. Fulfillment, shipping, and return data sync back to Shopify for customer visibility.
• Payment Handling – Shopify collects payment; F&O records the revenue. Settlement happens via Shopify Payments or third-party gateway.

Other Integrations:

• Amazon Seller Central – Connector syncs products and orders; F&O processes fulfillment.
• Custom APIs – Build integrations using Commerce OData endpoints (RESTful); any third-party system can query products and push orders.

Headless Commerce & APIs

Headless Commerce decouples the frontend from the backend. Instead of using Commerce’s React e-commerce storefront, you build a custom frontend (React, Vue, Angular, or mobile app) that calls Commerce APIs directly.

Headless API Endpoints:

• Product API – GET /products (search, filter, paginate); GET /products/{id} (details, variants, images, pricing).
• Catalog API – GET /catalogs (list categories and hierarchies).
• Cart API – POST /carts (create), GET /carts/{id} (view), POST /carts/{id}/items (add item), DELETE /carts/{id}/items/{lineId} (remove).
• Checkout API – POST /orders (finalize cart, collect shipping and billing, process payment).
• Inventory API – GET /inventory/{sku} (availability by location).

Benefits:

• Faster innovation cycles: Update the frontend without touching F&O.
• Mobile-first: Native mobile app uses the same APIs.
• Third-party frontends: Kiosk, AR/VR, or partner platforms can call the same APIs.

Omnichannel Fulfillment

Omnichannel fulfillment allows you to fulfill an online order from any location:

BOPIS (Buy Online, Pickup In Store):

• Customer orders online and selects a nearby store for pickup.
• F&O reserves inventory at that store.
• Store receives a pickup notification; associate picks and scans items.
• Customer arrives, provides order number, and picks up.
• POS completes the transaction and updates inventory.

Ship From Store:

• Online order arrives; system checks inventory across stores.
• If a nearby store has stock, shipping cost is lower than from warehouse.
• Store picks, packs, and ships directly to customer.
• Shipping label and tracking are generated in F&O.

Fulfillment Configuration:

• Assign each store to a warehouse or fulfillment group.
• Set fulfillment mode per store (BOPIS, ship-from-store, delivery, carry-out).
• Define distance radius for pickup eligibility (e.g., only offer pickup at stores within 5 miles).

Inventory Across Channels

Inventory in F&O is centralized in warehouses; channels consume from these warehouses:

• Physical Inventory – Units physically in stock.
• Allocated Inventory – Reserved for orders (picking not yet complete).
• Available Inventory – Physical minus allocated; what can be sold now.
• Channel-Specific Visibility – Warehouses are linked to channels. Online channel sees warehouse X inventory; retail store Y sees its own warehouse inventory plus accessible transfer warehouses.

Inventory Synchronization:

• POS queries CSU for current available inventory (sub-second latency from cache).
• Sale at POS triggers allocation; CSU updates CSU cache; F&O receives sync within seconds.
• Warehouse processes pick/pack; inventory physical count decrements; F&O updates allocation status.

Best Practices

• Channel Isolation – Keep channel configurations independent. Don’t assume changes to one channel won’t affect others.
• Price Strategy Clarity – Document which prices apply where: base prices for the default, channel-specific prices for overrides, promotion rules for time-limited discounts.
• Fulfillment Location Strategy – Decide in advance which orders are fulfilled from which warehouses. Use fulfillment groups to automate location selection.
• Inventory Accuracy – Perform regular cycle counts, especially for BOPIS and ship-from-store locations. Misaligned inventory causes customer cancellations.
• Payment Resilience – Test offline POS scenarios. Ensure CSU failover doesn’t break checkout.
• Catalog Maintenance – Remove discontinued products from channels promptly. Sync errors (e.g., Shopify out of sync with F&O) cascade to customer experience.
• Monitoring – Track channel-to-CSU sync health, POS transaction queues, and order-to-fulfillment lag. Set alerts for slow syncs or failures.

Frequently Asked Questions

What’s the typical response time for product lookup at POS?

Under 500ms with CSU cache. If CSU is offline or cache misses, POS queues the transaction locally and retries when connection is restored. Modern MPOS uses local SQLite; desktop POS uses channel database.

Can I return a Shopify order in-store?

Yes, if you set up a return channel in F&O linked to retail stores. Shopify order data imports into F&O; customer brings receipt to store; store processes return (inspection, restocking) in POS; refund is issued and Shopify is notified.

How do I handle pre-orders in Commerce?

Use inventory reservation or allocation by order status. Create a “Pre-Order” sales order type; when product arrives, change status to “Ready to Pick” and trigger fulfillment. Inventory stays on-hand until order is completed.

Can I use different currencies in different channels?

Yes. Each channel has a default currency (e.g., Online = USD, EU Retail = EUR). F&O converts prices using exchange rates defined in Accounts Receivable. The CSU caches currency-specific prices.

How is customer loyalty tracked across channels?

Loyalty is stored in the customer master in F&O. When a customer purchases in POS, online, or call center, the loyalty account (points, tier, balance) is updated. At checkout, customer can redeem points across any channel.

What happens if I close a store or migrate to a new POS system?

Deactivate the store in Commerce Headquarters; inventory transfers to a central warehouse. Migrate active inventory first; historical data stays in F&O for reporting. New POS authenticates to new store location; old POS is decommissioned.