Most retailers say "omnichannel" and run channel silos. Inventory in one system, customer in another, orders split between e-com and in-store. The result: returns to a different store than the purchase fail, customer service can't see the e-com order, and the loyalty program contradicts itself.
Unified commerce on Dynamics 365 + Customer Insights + Power Platform fixes this — when implemented with the right architectural discipline.
What "unified commerce" actually means
Three things, sustainably true:
- Single customer record across all channels and brands.
- Single inventory view — every unit visible to every channel in real time.
- Single order — regardless of where it was placed, it can be fulfilled, modified, returned anywhere.
This is harder than it sounds. The technology exists; the discipline is the rare part.
Dynamics 365 Commerce — what it actually does
D365 Commerce (built on F&O) provides:
- Store, e-commerce, call-center channels with a shared product / pricing / promotion engine.
- Modern POS (cloud + offline) with hardware support.
- Headless commerce APIs for custom storefronts.
- Distributed Order Management (DOM) for ship-from-store, pick-up, drop-ship.
- Loyalty and clienteling.
It's a heavy product. For retailers with $100M+ revenue and complex operations, it pays back. For smaller retailers, Business Central + a best-of-breed e-com may be the right fit.
The customer 360 problem
Most retailers have the customer fragmented across:
- E-commerce platform (anonymized + email).
- In-store POS (loyalty number, name).
- Call center (CRM contact).
- Marketing tool (email subscriber).
- Mobile app (device ID).
Customer Insights — Data is the unifier:
- Ingest from every channel (CDC where possible).
- Match and merge using a tunable matching policy.
- Generate unified profile with stable customer ID.
- Push back to operational systems so each channel sees the unified view.
This is the foundation. Without it, "unified commerce" is marketing fiction.
Inventory — the brutal truth
Real-time, accurate inventory is the hardest part of unified commerce. Patterns:
- Single source of truth — usually F&O, sometimes a dedicated inventory engine.
- Real-time availability calls from channels via the Inventory Visibility service.
- Reservation logic that prevents overselling across channels.
- Buffer stock policies by SKU and channel based on velocity and risk.
- Cycle counts at store level driven by Power Apps for staff.
Inventory accuracy below 95% breaks unified commerce. Accept this and invest in the operational discipline.
Distributed Order Management
DOM is the brain of fulfillment:
- Sourcing rules: ship-from-store, ship-from-DC, drop-ship, BOPIS.
- Optimization: minimize cost, maximize margin, minimize splits.
- Visibility: where every order is at every moment.
- Modification: address change, cancel, partial return — without breaking the customer experience.
D365 Commerce's DOM is solid; many retailers extend it via custom rules in Power Automate / Logic Apps.
Store operations on Power Apps
Store associates need apps that work on the floor:
- Stock lookup and inter-store transfer.
- Endless aisle ordering.
- Clienteling — view customer profile, recent orders, recommendations.
- Returns processing including originated-elsewhere orders.
- Tasks and audits driven from HQ.
Power Apps mobile (with offline support) is the right tool. Tied back to Dataverse + F&O.
Loyalty and personalization
Loyalty must be:
- Unified — same points, tiers, benefits in every channel.
- Real-time — earn at POS visible immediately in app.
- Personalized — driven by behavior, not just rules.
D365 Commerce loyalty + Customer Insights gives you this. Customer Insights — Journeys orchestrates personalized communication across channels.
Marketplace and dropship
Most retailers now sell on marketplaces (Amazon, eBay, target.com). Patterns:
- Each marketplace as a channel in DOM.
- Inventory and price feeds via API or feed files.
- Order ingestion into F&O via Logic Apps.
- Returns handled in your DOM, even if the marketplace is the customer-facing party.
Performance and seasonality
Retail traffic spikes on Black Friday, holiday, flash sales. Plan:
- Auto-scale on App Service Plans / AKS for storefronts.
- Pre-warm caches before promotional events.
- Read-replica strategies for hot data.
- DOM performance testing at 5x peak before peak season.
- Game days for the incident response team.
FAQs
Can we use D365 Commerce with our existing e-commerce platform? Yes. Many retailers run Shopify, Magento, BigCommerce or custom on the front end with D365 Commerce as the back-of-house OMS, inventory and merchandising platform.
How does this compare to Salesforce Commerce Cloud / SAP CAR? D365 Commerce is more tightly coupled to ERP (F&O) — strength when ERP is your record-of-truth, weakness when you want pure best-of-breed. Salesforce CC is stronger on storefront DX and personalization tooling. SAP is the choice if you're already on S/4.
What about Business Central for retail? Business Central handles back-office for SMB retailers (10–50 stores) with simpler operations. For complex multi-channel, multi-brand, multi-country retail, F&O / Commerce is the right tier.
Real-time customer profile — how real-time is real-time? Sub-second is achievable for the customer ID and core attributes; sub-minute for richer segments and scores. Plan the latency budget per use case.
We help retailers consolidate channels onto Microsoft Cloud. Book a unified commerce assessment with our retail practice.