Public developments and original analysis · Announcement date: · Sources
On October 20, Conexiom opened early-access applications for its Headless Platform. SDKs, a REST API and an MCP server are intended to embed order and invoice processing in manufacturers’ and distributors’ existing portals, CRMs and agents. This gives companies a way to place document processing where orders already arrive.
The product page says its MCP server returns structured fields from documents and applies customers’ existing rules. Those fields still need to be matched to product catalogues, customer prices and packaging agreements. Receiving an order in a familiar application leaves that interpretation work to be done.
Ten cartons may need an entry for 120 units
Consider a hypothetical repeat customer ordering ten cartons of a particular fitting. If the agreed pack contains twelve units and the ERP records individual units, the entry should be 120. A previous order for a similarly named item may have used a different pack. Reading “ten cartons” correctly therefore still requires finding the product and packaging agreement that applies to this order. This is an illustrative scenario, not a customer case.
The conversion also affects price interpretation. A carton price treated as a unit price can produce quantities and amounts that look plausible separately but do not belong together. Preparation for entry should retain the original quantity, unit and price, alongside the internal item code and conversion basis. When an agreed pack size is missing, the order can wait for clarification rather than let a guess determine the shipment.
An implementation using Mokyun for this system integration could start with order preparation: retrieve current pack sizes and price conditions from authorised ERP and customer records, assemble them with the original order for review, then update agreed fields after confirmation. This is a proposed design around the company’s existing systems; the ERP version, fields and update method need project-specific verification.
Conexiom’s REST API description includes consulting pricing, inventory and catalogue services during processing and notifying other systems of validation or exceptions. Companies could use that distinction to continue a complete order while holding one whose packaging needs clarification. The actual interfaces and supported scope remain subject to the documentation and validation available in an early-access project.
For an individual order, staff need to trace ten cartons to the 120-unit conversion, the applicable customer price and the saved record. Those relationships matter again when the customer changes the order or returns goods. Extraction reduces transcription; preserving the relationships keeps the order explainable after it enters the system.
Sources
Mokyun Editorial · neo@mokyun.com
