--- title: "AI Beside Microsoft Dynamics 365" canonical_url: "https://cognilium.ai/erp-ai" slug: "erp-ai" section: "erp-ai" page_type: "pillar" date_modified: "2026-09-29" description: "We build AI that runs beside the ERP you already run, Microsoft Dynamics 365, by a team that knows Finance and Operations, not just AI." publisher: "Cognilium AI" author: "Mudassir Marwat" person_same_as: - "https://www.linkedin.com/in/mudassir-marwat/" - "https://orcid.org/0009-0008-1927-2598" - "https://github.com/mudassirmarwat" - "https://medium.com/@mudassir-marwat" - "https://www.youtube.com/@mudassir-marwat" - "https://dev.to/mudassirmarwat" - "https://hashnode.com/@mudassirmarwat" - "https://huggingface.co/mudassirmarwat" - "https://bsky.app/profile/mudassir-marwat.bsky.social" - "https://substack.com/@mudassirmarwat" - "https://topmate.io/mudassirmarwat" - "https://fueler.io/mudassirmarwat" - "https://www.instagram.com/mudassirmarwat/" - "https://www.facebook.com/mudassir.marwat" - "https://www.reddit.com/user/mudassirmarwat/" - "https://www.f6s.com/member/mudassir-marwat" - "https://cognilium.ai/founder" answers: - "If your location data is reliable" - "If your location data is not reliable" entities: [] related: --- # AI Beside Microsoft Dynamics 365 **Location Truth** Fix inventory location accuracy at the source. A worker photographs a part or a shelf label, computer vision and OCR identify the item and the location, and the system updates Dynamics automatically. This is where most engagements start, because everything else depends on knowing where things actually are. ## In short **Location Truth** Fix inventory location accuracy at the source. A worker photographs a part or a shelf label, computer vision and OCR identify the item and the location, and the system updates Dynamics automatically. This is where most engagements start, because everything else depends on knowing where things actually are. **Warehouse Pick Optimization** Read your order history, work out where inventory should live so your team walks less, and push the changes into the system you already run. **Enterprise Knowledge Assistant** An internal assistant over your documents and your training videos, so people find an answer instead of sitting through a two-hour recording. Secured so a warehouse worker cannot see finance documents. Built to cost less than the per-seat licence of a generic copilot. **Transportation and Logistics** Route planning, proof of delivery, and a recommendation engine that picks the right vehicle for the load. Built on the same integration layer as the rest. We build AI that runs in tandem with the ERP you already use, Microsoft Dynamics 365, rather than a separate system your team has to learn. Most AI teams have never worked inside an ERP. Most ERP integrators cannot ship production AI. We do both, and that intersection is where the useful work lives. things we build on this integration layer Dynamics 365 products that share a name and little else supported integration surfaces, no workarounds Cognilium is not an ERP implementer, not a systems integrator and not a Dynamics reseller. Your partner owns the ERP. We own the decision layer that sits on top of it, and the work we do makes what they built worth more. **We never touch the ERP core** Every integration runs on the surface Microsoft supports: OData data entities, custom services and Business Events. Nothing is customised inside Dynamics itself, so nothing we build sits between your partner and their next upgrade. **Your partner owns the ERP. We own the decisions.** Dynamics is your system of record. Cognilium is your system of intelligence. We do not quote against your partner, do not review their build, and have no interest in the work they already own. **Nothing to unpick later** The fear with ERP customisation is that it becomes permanent: extensions nobody dares remove, and an upgrade nobody wants to run. Our apps are separate. Switch one off and the ERP runs exactly as it did before we arrived. Why the AI has to reach into the ERP, not sit in another tool Your ERP is where the work already happens. Anything that asks your team to leave it is competing with the job. Your ERP is where the work already happens. Inventory, orders, receipts, and locations live there. AI that sits in a separate tool asks your team to copy data back and forth, and adoption dies on that friction. AI that reads from the ERP and writes its results back means your team keeps working exactly as they do now, and the system just gets smarter underneath them. We add a missing layer. We replace nothing. Dynamics 365 is two different products that share a name and almost nothing else. Covers Sales, Customer Service, and Field Service. It is built on Dataverse and the Power Platform, with clean REST APIs. Covers Finance, Supply Chain Management, and Commerce. It is the real ERP core, with a different data layer, different APIs, and a different environment model. Your warehouse work lives in Finance and Operations, in Supply Chain Management specifically. A team that asks for the wrong environment, or that does not know an Entra app registration has to be registered inside Finance and Operations and mapped to a service role before a single API call will succeed, will spend weeks stuck before they touch a line of your data. We do not. Location Truth comes first on this list for a reason: everything downstream of it depends on knowing where things actually are. The standard, supported surface, not brittle workarounds — which is the difference between an integration that survives an update and one that does not. We use the standard, supported integration surface, not brittle workarounds. On Dynamics 365 Finance and Operations that means OData data entities for reading and writing master data, inventory, and locations, custom services for specific business logic, and Business Events for reacting to receipts and put-away as they happen. Authentication is service-to-service through an Entra app registration mapped to a Finance and Operations service role. Everything is built secure by design: least-privilege access, encryption in transit and at rest, and an audit trail on every interaction. You keep full ownership of the code and the data. Most engagements begin with one of two low-risk steps, and which one depends on a single question about your data. ## If your location data is reliable : send us twelve months of order lines if you have them, ninety days is enough to start, and a location master, and we tell you what your current placement is costing you. ## If your location data is not reliable We start there instead, because optimizing on data you cannot trust produces confident, wrong answers. Nothing here is invented. Every element is one of the integration surfaces named in the paragraph above. If your location data is reliable, send us the order lines and we will tell you what your current placement is costing. If it is not, we start there instead. Either way the first step is small and the answer is yours to keep. What Microsoft ships inside Dynamics, what it does not, and the engineering that starts where a general assistant runs out. --- Canonical HTML: https://cognilium.ai/erp-ai