Orders arrive through several channels
Email, portals and sales teams can leave operations with repeated entry. Scope each intake source and connect it to a validated order workflow.
B2B order management software
Keep every order moving, from quote to shipment.
Give the people selling, packing and answering customers a connected order record. Build your B2B order management workflow on Open Mercato's sales, catalog and shipment foundations.
MIT open source
1,928 stars on GitHub
50+ pluginsAn order should arrive with the context people need to fulfil it.
Inventory and order status drift apart
A customer promise depends on up-to-date information. Define the system of record and synchronization rules before adding availability and fulfilment views.
Packing and shipping create another handoff
Labels, packing notes and tracking details often live separately. Bring them into the same operational chain, with the carrier and ERP integrations your business uses.
A working foundation for the whole order record.
Quotes and confirmed orders
Convert commercial discussions into structured sales documents with customer and line-item context.
Pricing and adjustments
Use product, variant and channel pricing, taxes, discounts and document adjustments.
Partial shipments
Allocate quantities to shipments and keep remaining items visible against the order.
Connected fulfilment
Extend the process with carrier integrations, packing screens, background jobs and status updates.
Feature by feature
Every order detail, in a workflow that stays connected.
Compare manual order administration with the sales, pricing and shipment capabilities you can start with on Open Mercato.
| What your team gets | BUILT AROUND THE ORDEROpen MercatoSales + catalog + shipments | Spreadsheets + emailSeparate files and manual handoffs |
|---|---|---|
| Where Open Mercato adds control | ||
| Convert a quote into a linked order | ✓ | ×Copy and re-enter |
| Built-in product, variant and channel pricing | ✓ | ×Separate price files |
| Allocate order quantities to multiple shipments | ✓ | ×Manual reconciliation |
| Linked order, payment and shipment records | ✓ | ×Separate records |
| Application roles and feature permissions | ✓ | ×File access only |
| Capabilities available in both | ||
| Record customer orders and line items | ✓ | ✓Manual records |
| Calculate prices, taxes and discounts | ✓ | ✓Manual formulas |
| Implementation and scope | ||
| Synchronize order data with your ERP | ↗ERP integration | ×Manual handoff |
| Carrier labels and tracking updates | ↗Carrier integration | ×Manual coordination |
Available in the stated scope Not included in this model Requires implementation
Baseline: separate spreadsheets and email, without an integrated order-management application. Inventory synchronization, carrier connections and financial integrations are scoped per implementation.
Reviewed 12 November 2026. Sources: Sales documentation · Shipment documentation · Open Mercato core · Customer records
Explore implementation and commercial details
| What matters | Order-management requirement | Open Mercato |
|---|---|---|
| Order intake | Which channels create the order and who validates it? | Sales APIs and extensible workflows support the intake integrations you scope. |
| Commercial context | Can pricing, discounts and taxes be explained? | Catalog pricing and sales adjustments keep the calculation attached to the record. |
| Partial fulfilment | Can one order ship in several parts? | Multiple shipments can fulfil quantities from the same order. |
| Tracking | Where can customer service see a shipment update? | Shipment records can be connected to carrier and ERP integrations. |
| System ownership | Where do stock, invoicing and financial truth live? | Define those boundaries in the project and connect the appropriate systems. |
MDM NT · manufacturing implementation
Packing, labels and tracking became one connected process.
MDM NT introduced a packing workspace, batch label jobs and carrier tracking through Open Mercato. The integration made the shipment information available in its existing ERP.
Read the MDM NT story ↗
Prove the flow on a representative set of orders.
Map the order journey
List intake channels, pricing decisions, approvals, fulfilment steps and customer notifications.
Connect the master data
Map customer, SKU, tax, carrier and ERP identifiers. Decide how stock and financial records will be synchronized.
Test the exceptions
Rehearse partial shipments, cancellations, price changes, returns and failed integration calls as required by your business.
Roll out with operations
Start with one channel or warehouse, reconcile transactions and train the team that handles exceptions.
Questions before you take the next step.
Does it connect to our carrier?
Carrier-driven shipment creation requires a configured carrier integration. Review the carriers and services you use during scoping, then test labels, status updates and exception handling.
Can it handle split shipments?
The Sales module supports multiple shipments against an order, with quantities and remaining fulfilment visible. Your warehouse process can build on that foundation.
Can we connect our B2B portal or ERP?
Yes, integrations can be implemented through the API and extension architecture. The work depends on each system's interface, identifiers, data ownership and synchronization requirements.
Is warehouse inventory included in every deployment?
Inventory and warehouse requirements should be scoped alongside order management. Define reservations, locations, units, picking and stock ownership before choosing the modules and integrations for production.
Bring your most difficult order exception.
A split shipment, a custom price or a missing tracking update is a useful starting point for a focused implementation conversation.
Discuss your order workflow
Talk through your process, integrations and implementation needs with the Open Mercato team.