Dynamics 365 Commerce Connector — Loyalty & Rewards Integration

About the project We are a customer-loyalty and engagement SaaS platform used by retail and e-commerce brands. Our platform already ships native connectors for several major commerce platforms, and we are now building a Microsoft Dynamics 365 Commerce connector to serve enterprise retail clients running both an online store and physical stores. We are looking for a senior D365 Commerce engineer (or a small team) to build this connector end-to-end against our documented REST API and webhooks. (Our company name and full API documentation are shared with shortlisted candidates under NDA.) What you'll build A config-driven, reusable connector — not a one-client customization. Every client-specific value (API credentials, channel/store mapping, tender and discount configuration, earn-rule mapping) must be Headquarters configuration, not hard-coded. The connector will be deployed to a pilot client's environment first, with AppSource certification as a possible later phase. The connector spans four surfaces: Commerce Scale Unit / Commerce Runtime (CRT) extension — server-side request handlers and custom Retail Server APIs that broker all calls to our platform. Store Commerce app extension — POS operations, custom controls, and receipt changes for the in-lane experience. E-commerce online SDK module — storefront modules/data actions surfacing balance, tier, and available rewards. HQ (F&O) configuration model — parameters forms, channel mapping, and secure credential storage. Key integration points (v1 scope) 1. Customer identity & profile sync Create/update a loyalty profile when a customer is created or updated in Commerce (online registration, POS enrollment, HQ import). Pass a shared merge key (mobile number and/or email) so the same shopper resolves to one loyalty profile across e-com and every store. Handle guest checkout and post-hoc identification at the till. Bulk/batch load of the existing customer base at onboarding. 2. Earn — online orders On order confirmation in the online channel, send the order to our Orders API (line items, prices, discounts, categories, currency, channel). Award points/cashback and reflect the updated balance on the storefront. 3. Earn — in-store transactions On sale completion at the POS, send the retail transaction to our Orders API. Must work correctly with the async posting path (Commerce Data Exchange / statement posting) — decide and justify whether earn fires at tender time, on transaction upload, or both. 4. Redeem — checkout and POS Real-time balance and available-rewards lookup for the identified customer. Apply redemption at checkout: points-to-value conversion applied as a discount or custom tender line (your recommendation required — this is the design decision we care most about). Secure in-lane redemption using OTP or QR validation. Hold / burn pattern: points are reserved when redemption is applied and only burned once the sale is tendered and posted; released if the transaction is voided or abandoned. 5. Coupons & promotions Support both modes: our platform issues coupon codes, and "bring your own engine," where we call an endpoint in Dynamics so the existing D365 Commerce discount engine remains authoritative for pricing and finance reconciliation. Coupon validation and redemption at both channels. 6. Returns, refunds & voids Full and partial returns must reverse the corresponding points and reinstate redeemed value. Voided and suspended transactions must not leak held points. 7. Webhooks — inbound Consume our webhooks (balance, tier change, coupon issued) and surface the result to the POS and storefront. 8. Reliability & operations Idempotency on every earn call, keyed on transaction/receipt ID — retries must never double-award. Loyalty calls must be non-blocking: a slow or unavailable loyalty API must never block payment authorization or hold the lane. Retry, dead-letter, and correlation-ID logging for support triage. Two things we will ask about in the interview These sink most D365 Commerce loyalty projects, so please address them in your proposal: Offline mode. Store Commerce runs offline against the local channel database. Explain exactly how earn and redeem degrade when the lane has no connectivity, and how state reconciles when it comes back. Coexistence with native D365 Commerce loyalty. Dynamics ships its own loyalty engine. Explain your approach to bypassing, disabling, or coexisting with it without breaking pricing, tender, or statement posting. Deliverables Deployable extension packages (Commerce Scale Unit extension, Store Commerce app extension installer, online SDK modules) built and deployed via LCS. HQ configuration model and setup forms. Source code in our repository, with a clean build pipeline. Technical documentation: architecture, configuration guide, deployment runbook, troubleshooting guide. Unit and integration tests, plus a demo environment walkthrough. Handover session with our engineering team.