Hire Microsoft Dynamics 365 experts
Hire Microsoft Dynamics 365 Commerce developers and consultants
In short
MS Dynamics Guys provides Microsoft Dynamics 365 Commerce specialists in two tracks. A functional consultant configures channels, pricing, customer orders and statement posting in Commerce headquarters. A developer builds and tests extensions for the Store Commerce app, the Commerce runtime (CRT) and headless Commerce application programming interfaces (APIs). Your lead sets priorities for both tracks. If you sell through Microsoft Dynamics 365 Business Central and a storefront connector, we recommend a different role.
When a Commerce specialist from MS Dynamics Guys fits
Commerce work has two sides. Retail process design lives in the configuration of Commerce headquarters. Commerce code lives in extensions. Most gaps start on one side, and a store rollout often needs both.
Team situations that call for a Commerce specialist
- Store and online prices disagree. Price groups, affiliations and discounts overlap, and nobody can say which price a customer will pay.
- Statements stop posting. Store transactions reach headquarters, but statements fail on tender differences, and store finance waits.
- A store rule needs code. Your process owner wants a check at checkout that configuration cannot express.
- Inherited code runs on retired tools. A previous partner built extensions with the Retail software development kit (SDK), or some registers still run Modern POS. Microsoft ended support for both in October 2023.
- A new store or channel is coming. The rollout needs registers, screen layouts, an extension package and test scripts, but your team has no Commerce time left.
When another role or service fits better
- You sell through Microsoft Dynamics 365 Business Central and an online store connector, such as the Shopify Connector. That is not Commerce work. A Business Central consultant sets up the connector. A Business Central developer writes extensions in AL, the programming language of Business Central, for any gaps.
- The gap is the general ledger behind statement posting: accounts, legal entities or the period close. A Microsoft Dynamics 365 Finance consultant fits better.
- The gap is warehouse work in distribution centers, such as receiving, picking and shipping. A Microsoft Dynamics 365 Supply Chain Management consultant fits better.
- Your backlog is X++ code, the programming language of finance and operations apps, for Finance or Supply Chain Management processes outside Commerce. A finance and operations developer fits better.
- You want a whole store rollout delivered: setup, devices, training and go-live. That is a Microsoft Dynamics 365 Commerce implementation project, not a hire.
- Nobody on your side can decide prices, store processes or release dates. A specialist can prepare options but cannot make those decisions.
Retail process design or Commerce code: which track closes the gap?
Find the row that matches your situation. The track column shows where to start, and the last column shows what your team provides.
| Gap in your program | Track | What the specialist owns | What your team provides |
|---|---|---|---|
| Point of sale prices differ from online prices | Functional | Price groups, trade agreements and discounts, with a test case for each price scenario | A pricing owner who approves each price rule |
| Statements fail to post, or post with differences nobody can explain | Functional first; a developer only when an extension causes the error | Statement setup, trickle feed posting, store difference limits and a daily checklist | A store finance owner who decides how differences are handled |
| A check at checkout that configuration cannot express | Developer | A Store Commerce extension and a CRT trigger, with tests | An approved design and the owner of the rule |
| A new text field that cashiers fill in on a sale or a customer order | Functional | Order attributes defined in headquarters and linked to the store, and the Attributes panel on the screen layout. Capturing the value needs no new tables or code. A rule that uses the value still needs a developer. | An owner who decides which fields cashiers fill in |
| Store data that order attributes cannot hold, such as a new set of records that headquarters must keep | Developer with X++ skills | A channel database table, the matching headquarters table in X++ and the Commerce Data Exchange (CDX) job between them | Access to your Lifecycle Services project and a reviewer for X++ code |
| A new store, new registers or a new channel goes live | Both tracks | Channel and register setup, screen layouts, the extension package and go-live test scripts | A store operations lead who owns the opening date and signs acceptance |
If no row matches, describe the gap in your role brief. We say which track fits, or tell you when a different role or a project fits better.
Work a Commerce functional consultant can own
The consultant configures Commerce headquarters and proves each setting with a test. Your owners decide the business rules behind the settings.
| Area | What the consultant delivers | What your team decides |
|---|---|---|
| Channels and assortments | Retail, call center and online channel records, with their payment methods, assortments and place in the organization hierarchy | Which channels sell which products, and when each channel opens |
| Prices and discounts | Price groups for channels, affiliations, loyalty programs and catalogs, plus trade agreements, price adjustments, discounts and a pricing test sheet | Every price and discount rule, approved by your pricing owner |
| Store setup | Functionality profiles, registers and devices, screen layouts with the POS operations each role needs, and order attributes for extra text fields on orders | Store rules such as returns, manager approvals and what each role may do |
| Customer orders | Modes of delivery, including a pickup mode, fulfillment groups and asynchronous order creation, the mode Microsoft recommends | Which stores ship orders, which offer pickup, and the deposit rules |
| Jobs and statements | Distribution schedules for the jobs that move data, trickle feed posting and the store limits for posting differences | The difference limits, and who reviews a statement that fails |
| Testing and training | UAT scripts for each role, test data in a sandbox, a defect log, and short guides for cashiers and store managers | Who tests, who signs off and when each store is trained |
Configuration comes first. Before anyone writes code, the consultant checks standard settings and functionality profiles. A requirement that still needs code goes to the developer with a written acceptance test.
Need this track only? Describe the functional consultant role.
Work a Commerce developer can own
The developer builds with the Commerce SDK in your repository. Each item ends with code, tests and a package. A second engineer reviews every pull request before it reaches a shared environment: your reviewer, or one named in the agreement.
| Area | What the developer delivers | Where the role stops |
|---|---|---|
| Store Commerce extensions | Custom views, controls and operations in TypeScript, and triggers that run before or after a POS operation | Button placement on screen layouts stays in headquarters configuration |
| Commerce runtime logic | Pre-triggers and post-triggers on CRT requests, and new CRT services, in C#. A handler is overridden only when the standard logic must be replaced. | Your process owner decides the business rule |
| Headless Commerce APIs | New APIs in C#, hosted in the CSU, for POS or e-commerce clients | Modules of the online storefront itself need a front-end developer. Middleware, monitoring and reconciliation between Commerce and your other systems belong to an integration engineer. |
| Channel database tables | New tables in the extension schema of the channel database, delivered in the CSU package | Data that headquarters must keep also needs work in headquarters |
| Headquarters code and data sync | X++ for Commerce headquarters: new tables, the Commerce Data Exchange (CDX) jobs that move their data, and extensions to Commerce logic such as statement posting | X++ for Finance or Supply Chain Management processes belongs to a finance and operations developer |
| Packages and releases | A CSU extension package and release notes. Registers with the in-app deployment of Store Commerce run their POS content locally, not from the CSU. They also get an extension installer with the POS extension and the CRT and database extensions that offline mode uses. | Your release approver chooses each deployment window |
| Integration and regression tests | Unit tests for CRT logic, integration tests against a test copy or stub of each outside service, and scripted POS tests, run online and offline | Store UAT stays with your store team |
Need this track only? Describe the Commerce developer role.
How MS Dynamics Guys assesses each Commerce track
Consultants and developers fail in different places, so each track has its own exercises. A reviewer from the same track checks the work and asks the candidate to explain each choice. You receive the written result before your interview.
| Skill | How we review it | Evidence you receive |
|---|---|---|
| Functional: pricing logic | The candidate predicts what a customer pays when price groups, pricing priorities and an affiliation overlap, then names the setting that changes the result | A worked example with the reason for each price |
| Functional: customer orders | From a one-page brief, the candidate configures pickup in store in a sandbox and writes the test script | The configuration list and a test script that a store team could run |
| Functional: statements | The candidate traces one cash sale from upload to a posted statement, then explains a tender difference that stops posting | An annotated trace that names each job, statement and limit |
| Developer: CRT design | The candidate reviews a sample CRT extension and chooses between a trigger and a handler override. They also flag any use of CRT business logic classes. Microsoft says these classes are not backward compatible, so extensions that use them can break in an upgrade. | Review notes ranked by risk |
| Developer: offline behavior | The candidate builds a small POS dialog that calls CRT logic, with tests for online and offline use | Code, tests and a note on what happens offline |
| Developer: release planning | The candidate plans one extension package across a service update: build version, update order and sandbox tests | A version plan for headquarters, the CSU and registers |
Only candidates who pass their track's exercises are introduced. A pass in one track says nothing about the other. Comparing Commerce candidates from several suppliers? Give each one the same exercise from the table above. Score it with the four-level rubric in the buyer scorecard for Microsoft Dynamics 365 specialists.
Illustrative first work packages, one per track
One specialist, a consultant and developer pair, or an owned rollout wave
Choose by who should plan each store release and who should answer for its result. Hours, allocation, notice, minimum term, replacement and the rate basis are agreed in writing for each engagement. To weigh the models for your own stores, use the decision worksheet on staff augmentation versus project delivery.
One specialist in your team
A consultant or a developer works from your backlog under your lead. You answer for the result, and the specialist answers for the quality of their own work.
Can a Commerce developer from MS Dynamics Guys work in our repository, Lifecycle Services project and store release windows?
Yes, once you grant named access and agree in writing who reviews code and who approves each deployment. The developer commits to your repository, builds packages from it and prepares each release. Your release approver decides when a package reaches production. Each step below adds a Commerce check, such as offline registers or release windows, to the general path from role brief to shortlist. Your access setup and release calendar set the pace, so this page gives no shortlist or start date.
Your role brief
Name the track, your Commerce version, the channels and stores in scope and where the CSU runs: in the cloud or in your stores. Say whether registers must work offline, and whether you deploy through Lifecycle Services or the Power Platform admin center preview. Add your repository, release calendar and working hours.
Fit review
We tell you whether the gap is configuration, code or both, and whether we can staff the role, before anyone is introduced.
Results by track
Each candidate profile names the track the candidate passed: functional, developer or both.
Your interview
Your lead and a reviewer who knows your code or your store processes interview each candidate, ideally on a real Commerce item from your backlog. You decide who joins.
Written agreement
For Commerce, it names the code reviewer and who approves each CSU deployment and its downtime window. It also names who signs UAT for each store and who stays reachable when stores open after a release. Allocation, overlap hours, notice, minimum term, replacement, the rate basis, confidentiality and ownership of the work are agreed in the same document.
Named access
Your administrator issues named accounts for the repository, a development environment, a sandbox and your Lifecycle Services project, with only the roles the work needs. Production access comes only when a task requires it. An onboarding checklist for external specialists helps you prepare these accounts before day one.
First task accepted
A small real item, such as one extension or one configuration change, passes review and your acceptance criteria before larger work starts.
Release windows. Microsoft says an update or an extension to a cloud CSU causes downtime of up to an hour, and sometimes two hours or more. During that time, cloud channels stop. Registers with offline mode keep working with fewer functions, and e-commerce clients that depend on the CSU are disrupted. As Microsoft advises, the developer times the same deployment in a sandbox first. Your release approver then sets a production window with your store operations lead. An extension and a pending update can share one window and one downtime.
Lifecycle Services. Since February 16, 2026, new customers of Finance, Supply Chain Management and Project Operations start cloud projects in the Power Platform admin center. Commerce projects are still created in Lifecycle Services. CSU packages are uploaded to your project's asset library before deployment, so the developer needs a named account in that project. Microsoft is also previewing Commerce deployment in the Power Platform admin center. Microsoft advises starting that preview in sandboxes and keeping production CSUs and e-commerce in Lifecycle Services until general availability.
Evidence you can check, and a worked pricing demonstration
This page names no clients and shows no reviews, profiles or case studies.
How we assess specialists explains the scoring levels, who reviews each exercise and what an exercise cannot show.
The table below works through the pricing exercise once. MS Dynamics Guys wrote it from Microsoft's documented pricing rules, and you can rebuild it in a sandbox. A jacket has a base price of 120.00, and its trade agreements have Find next set to Yes. Price group REGION has priority 0 and a price of 110.00 in both stores. Price group CITY has priority 5 and a price of 125.00 in the city store only. Price group STAFF has priority 0, a price of 95.00 and a staff affiliation.
| Situation | Price charged | Why |
|---|---|---|
| Walk-in customer in the regional store | 110.00 | A trade agreement price is used before the base price, and REGION is the only price group there |
| Walk-in customer in the city store | 125.00 | CITY has the higher priority. Its price is found first, so the lower REGION price is ignored |
| Staff member in the regional store | 95.00 | STAFF and REGION share priority 0, so the lower price wins |
| Staff member in the city store | 125.00 | The CITY price is found at priority 5, so the STAFF price at priority 0 is not considered |
| Staff member in either store, after STAFF gets priority 10 | 95.00 | STAFF is now evaluated first in both stores |
Row 4 shows why priorities need care: a price found at a higher priority hides every lower one, including a staff price. In the assessment, the candidate predicts each price before the reviewer reveals it, then names the setting that changes it. Microsoft advises using pricing priorities sparingly, because each priority adds a full pass of the pricing logic. Discounts follow their own priorities, separately from prices.
This is an original demonstration. It is not a client configuration, and it is not a candidate's answer.
Questions about hiring Microsoft Dynamics 365 Commerce specialists
Do we need a Commerce consultant, a developer or both?
Start from where the problem shows. Wrong prices, failed statements, missing POS buttons and store processes that do not fit your business are configuration problems for a functional consultant. A rule that configuration cannot express, such as a check against an outside system at checkout, needs a developer. If you want one person for both tracks, say so in the role brief. That candidate must pass both sets of exercises, and you receive a written result for each.
Is Microsoft Dynamics 365 Commerce the same as a Business Central store connector?
No. Commerce is one of the finance and operations apps. Its back office, Commerce headquarters, runs on the same platform as Finance and Supply Chain Management. Commerce adds the CSU, the Store Commerce app and an e-commerce storefront. A Business Central connector works differently. Microsoft's Shopify Connector, for example, links a Business Central online company to a Shopify store, with no CSU and no Store Commerce registers. That work belongs to Business Central consultants and Business Central developers, not to Commerce specialists.
Do Commerce extensions keep working offline and through service updates?
Offline, only where the deployment supports it. The Store Commerce app for Windows works offline in its in-app deployment, with a local database and a local copy of the CRT. Its hybrid deployment and Store Commerce for web do not work offline. Neither do the Android and iOS apps from the app stores. Offline mobile registers need a custom app built with the Store Commerce SDK. An extension that must work offline is installed on each of those registers, and calls to outside services need an agreed offline rule.
Through updates, the risk is managed, not removed. Microsoft ships four service updates a year for finance and operations apps, including Commerce headquarters, and you must take at least two. Headquarters updates first, then the CSU, then the registers. In-app registers update through the Store Commerce installer, register by register. Microsoft is also gradually turning on automatic updates for cloud CSUs. Before each production update, the developer checks the packages against the new version and runs your tests in a sandbox.
Who owns payment compliance in a Commerce project?
Your company does, together with your payment provider. MS Dynamics Guys makes no Payment Card Industry (PCI) compliance promise, and our specialists do not handle card data. A consultant can set up payment methods for each channel and test tender declarations at shift close. A change to the payment flow or the payment connector is designed with your payment provider. Your compliance owner signs it off before anyone builds it.
Our stores are open in the evenings and on weekends. When must the specialist be reachable?
Overlap hours are set per engagement, so start from the store events the role supports. Put your store hours and time zones in the role brief, and we check them before any introduction. The written agreement then records the overlap. A developer should be online during each production deployment and when stores open after it, because cloud channels stop during the CSU downtime. A consultant who changes statement or shift settings should review the first statements that post after the change.
How do our stores, registers and extensions change the cost?
Your Commerce setup decides how many hours the work takes. Each channel and store that changes adds configuration and store tests. Registers that must work offline add tests in offline mode. Each extension you keep needs package checks and sandbox tests before every service update you take. The rate basis, allocation and term are agreed in writing for each engagement, so no rates appear here. If a production deployment must run after the stores close, the agreement also sets how those hours are billed. For the developer track, seniority and engagement length change the cost of hiring a Microsoft Dynamics 365 developer too.
Which Commerce packages, scripts and records stay with us when the engagement ends?
Everything the work produced stays in your own systems. Code stays in your repository with its history. Each CSU package stays where you deploy it from: your Lifecycle Services asset library or your Power Platform admin center environment. Test scripts and two Commerce records stay in your workspace. The configuration list names each channel, functionality profile, screen layout and price group that the work changed. The version plan shows the release on headquarters, the package on each CSU and the registers that need the extension installer. The handover note adds open items and the deployment order: headquarters, then the CSU, then the registers. Ownership of the work is set in the agreement. On the last day, your administrator removes the specialist's accounts, including the one in your Lifecycle Services project.
Discuss the Commerce role
Tell us your Commerce version, the channels and stores in scope, whether registers run offline and what waits in your backlog. Name the track you need, or describe the gap and we suggest one before anyone is introduced.
Product documentation referenced on this page
- Microsoft Dynamics 365 Commerce architecture overview Microsoft Learn, checked October 4, 2026
- Channels overview (Commerce) Microsoft Learn, checked October 4, 2026
- POS user interface visual configurations Microsoft Learn, checked October 4, 2026
- Retail sales price management Microsoft Learn, checked October 4, 2026
- Customer orders in point of sale (POS) Microsoft Learn, checked October 4, 2026
- Retail statements Microsoft Learn, checked October 4, 2026
- Store configurations for Retail statements Microsoft Learn, checked October 4, 2026
- Trickle feed-based order creation for retail store transactions Microsoft Learn, checked October 4, 2026
- Define and set order attributes Microsoft Learn, checked October 4, 2026
- Download Commerce SDK samples and reference packages from GitHub and NuGet Microsoft Learn, checked October 4, 2026
- POS extension overview Microsoft Learn, checked October 4, 2026
- Commerce runtime (CRT) extensibility Microsoft Learn, checked October 4, 2026
- Enable custom Commerce Data Exchange synchronization via extension Microsoft Learn, checked October 4, 2026
- Create a Cloud Scale Unit extension package Microsoft Learn, checked October 4, 2026
- Microsoft Dynamics 365 Commerce component versioning requirements Microsoft Learn, checked October 4, 2026
- Apply updates and extensions to Commerce Scale Unit (cloud) Microsoft Learn, checked October 4, 2026
- Lifecycle Services project creation freeze Microsoft Learn, checked October 4, 2026
- Manage Microsoft Dynamics 365 Commerce deployments in Power Platform admin center (preview) Microsoft Learn, checked October 4, 2026
- Store Commerce app Microsoft Learn, checked October 4, 2026
- Create a Store Commerce extension installer package Microsoft Learn, checked October 4, 2026
- Store Commerce app for mobile platforms Microsoft Learn, checked October 4, 2026
- Offline point of sale (POS) functionality Microsoft Learn, checked October 4, 2026
- Service update availability (finance and operations apps) Microsoft Learn, checked October 4, 2026
- Shopify Connector overview (Business Central) Microsoft Learn, checked October 4, 2026
- Programming in AL Microsoft Learn, checked October 4, 2026
- X++ language reference Microsoft Learn, checked October 4, 2026