Distribution software: how ERP, WMS and EDI fit

Distribution software for a wholesaler is four layers, each owning a different record. The ERP holds items, customers, prices, on-hand quantity, costing, purchasing, and the general ledger. Warehouse execution holds bins, directed put-away, and scanner picks. EDI holds trading-partner documents and labels. A portal holds customer self-service orders.

As of October 2026, Microsoft lists Business Central Essentials at USD 80 per user per month in the United States, paid yearly. Orderful lists web EDI fulfillment at USD 189 per month per trading partner. For a 30 to 100 person wholesaler, buy one ERP that posts inventory to the ledger, turn on barcode picking if the floor is still on paper, and add EDI only for partners who require it. A separate warehouse product waits until directed put-away, labor tracking, or automation outgrows the warehouse documents inside that ERP.

Wikipedia describes distribution software as covering order processing, logistics, inventory, and, in more advanced products, forecasting, warehouse management, pick-pack-ship, EDI, and trade spend. That definition is a feature list. The buying decision is which of those jobs you pay for now, and which system is allowed to be the master of the item, the bin, and the partner document.

What each layer of distribution software owns

A stack fails when two products both believe they own on-hand quantity. Split the jobs before you split the vendors.

The ERP is the commercial and financial system. It creates the item, the customer, the price list, the sales order, the purchase order, the receipt into inventory quantity, the shipment that relieves quantity, the invoice, the cost, and the journal entry. If a number has to hit the general ledger, it starts here. Business Central and Odoo both do this job for a distributor. Which product fits your company is a separate choice. Our best ERP for wholesale distribution guide compares that choice. This page stays on sequence: what you turn on together, and what you add later.

Warehouse execution is how a person on the floor finds a bin, scans a unit, and confirms a pick. Business Central does not sell that as a separate WMS product. Warehouse setup is a configuration of the same system, from posting directly on orders, to basic inventory put-away and pick, to advanced warehouse receipts, shipments, and picks, and then to directed put-away and pick, where bins are mandatory. Microsoft's warehouse design notes say to turn the heavier options on only when they improve the process, because complexity rises with more people and more steps.

Odoo Inventory, included with the all-apps subscription, documents locations and shelves, putaway rules, single, batch, cluster, and wave picking, barcode scanning with GS1, EAN-13, and EAN-14, multi-warehouse, drop-ship, cross-dock, FIFO, FEFO, and LIFO removal, landed costs, and FIFO, average, and standard costing. The same inventory feature page says the API can connect 3PLs, scales, scanners, and RFID. That is a wide warehouse layer. It is still the ERP's inventory app, configured in stages, until a site needs a dedicated execution system.

EDI is the pipe to a trading partner. Orderful lists the channels as AS2, SFTP/FTP, and VAN, and the standards as X12 and EDIFACT. The customer's supplier manual decides which documents and which label format you must send. Ask each partner for that manual and price that set as its own line. A checkbox labeled EDI on a product page is not proof that a given retailer will accept your files.

A customer portal is self-service ordering and shipment tracking for accounts that will not send EDI. Odoo states that portal users, such as customers placing ecommerce orders or tracking deliveries, are not paying users. The portal is worth buying when phone and email orders dominate and those customers are not already paying you through an EDI connection.

One field that looks like warehouse software and is not: the Shelf No. on a Business Central item or stockkeeping unit. It copies onto documents and reports. It is not used in warehouse activities or availability. If pickers are walking from a shelf number printed on a document, the field is still only a printed note, and directed picking is not running.

What a 30 to 100 person wholesaler should buy first

Buy in this order.

1. One ERP that posts inventory quantity and cost to the general ledger. Two ledgers, one in accounting and one in a warehouse app, will drift the first week someone receives a short shipment.
2. Barcode put-away and pick inside that ERP if the floor still runs on paper. Use the warehouse level that matches the building you have, not the level a demo warehouse used.
3. EDI only for trading partners who require it, with the document list and the label format written into the quote.
4. A separate WMS when directed put-away, labor measurement, or conveyor and automation work no longer fit the ERP warehouse documents.
5. A portal when sales spends the day re-keying retailer orders that will never arrive as EDI.

A buyer on a US wholesale thread put the starting point in one sentence: "Currently we use quickbooks Enterprise to manage inventory, sales and accounting, but it's not a very smooth solution." The same post says, "We manage inventory in a warehouse and employ several sales people." Both lines are from a wholesale software thread. That pattern, a small-business ledger plus a warehouse plus a sales team, is the common stack this page is replacing. It is also the pattern that gets expensive when each new job becomes another subscription and another item mapping.

For a single-entity distributor with no manufacturing and no service jobs, Business Central Essentials is usually the license that matches the work. Premium is the step up when people need service management or manufacturing. Confirm that split against your own routings and service orders before you pay the higher list price for every user.

When the warehouse inside the ERP is enough

Stay on the ERP warehouse documents while the team can name and zone the bins, a scanner can confirm the pick, and no automated storage needs its own software. Move when labor standards, a large zone crew, or a machine task feed no longer fit those documents.

Business Central's path is a ladder, and you can stop on a rung.

• Post on the order (What the floor does: Receive and ship by posting the purchase or sales document · When it fits: A cage, a mezzanine, or a room where the same person who enters the order walks the goods)
• Basic inventory put-away and pick (What the floor does: Record where stock went and what was picked · When it fits: You need a location history and a pick document, and bins are still simple)
• Advanced warehouse receipts, shipments, and picks (What the floor does: Break receiving and shipping into warehouse documents · When it fits: The office posts invoices and the floor works a different document)
• Directed put-away and pick (What the floor does: The system chooses the bin. Bins are mandatory · When it fits: You need bin types, ranking, capacity, zones, and FEFO, and you will staff the extra steps)

Directed put-away and pick adds bin types (RECEIVE, SHIP, PUT AWAY, PICK, PUTPICK, QC), bin ranking, quantity, cubage, and weight limits, zones, warehouse classes, put-away templates, and FEFO picking. Those controls earn their keep in a building that already loses product to the wrong bin or expires stock in the wrong order. They slow a five-person warehouse that was shipping fine from a printed list. Read the warehouse activity design against a week of your own receipts before you enable the top rung.

Odoo can run multi-warehouse, wave picking, and GS1 barcodes inside Inventory. A 3PL connection is the point to test on your data. Outside software that calls Odoo is an external API call. Carrier calls that Odoo itself makes to UPS, FedEx, and DHL stay on the Standard plan. A 3PL, a scale server, or an EDI platform that calls Odoo's JSON-RPC or XML-RPC API is the external API, which the pricing page places on the Custom plan. Have the bidder show the call direction on a diagram before you choose Standard.

Our warehouse management system explained page goes further on WMS scope. Use it when the ladder above is no longer the question, and the question is whether a second product should own the bin.

What Business Central and Odoo licenses cost in October 2026

Licenses are the predictable half of the budget. Services, connectors, and partner-document testing are not on these pages. Microsoft also says the figures on its pricing pages are informational and may differ at checkout because of currency, country, and regional variants. Licenses are bought through a Cloud Solution Provider. Paid user types named in the licensing article are Essentials, Premium, Team Member, and External Accountant. A Device license lets several people share a licensed warehouse, shop-floor, or point-of-sale device, up to the number of device licenses purchased at the same time. As of October 2026, the US and Canada pricing pages do not list a Device price or an External Accountant price. Ask the Cloud Solution Provider for both before you budget the floor.

• Business Central Essentials (United States, per user per month, paid yearly: USD 80 · Canada, per user per month, paid yearly: CAD 108.50, plus applicable tax)
• Business Central Premium (United States, per user per month, paid yearly: USD 110 · Canada, per user per month, paid yearly: CAD 149.20, plus applicable tax)
• Business Central Team Members (United States, per user per month, paid yearly: USD 8 · Canada, per user per month, paid yearly: CAD 10.90, plus applicable tax)

Essentials is business management for finance, sales, and operations, with Copilot included. Premium includes Essentials plus service management and manufacturing. Team Members are limited read, approval, and selected create or update access. They are the wrong license for someone who receives, picks, and adjusts inventory all day. Sources: US Business Central pricing and Canada Business Central pricing, both as of October 2026.

Odoo's public pricing page, as of October 2026, lists these amounts in USD. Standard is listed at USD 31.10 per user per month beside USD 38.90. Custom is listed at USD 61.00 beside USD 76.20. The note on the page says the discount is valid for 12 months for the initial users ordered. Standard is Odoo Online and all apps. Custom adds Odoo.sh or on-premise, Studio, multi-company, and the external API. Odoo.sh hosting is not included in the user price. A Light User is listed at USD 8.90 and the rights include Inventory Barcode Operator. Ask for the CAD figure on your own quote if you pay in Canadian dollars. Plans include hosting, maintenance, and email support. They exclude implementation services, Odoo.sh hosting for custom development, in-app credits, and maintenance of custom code. Source: Odoo pricing, October 2026.

Assume 25 people who create orders, receipts, and invoices, 10 warehouse people who only scan, and no manufacturing.

On US Business Central Essentials, 25 users at USD 80 is USD 2,000 per month, or USD 24,000 per year, paid yearly. The 10 scanners are not covered by that line. If they share devices, budget a Device license count with your reseller, because no list price was on the pricing page. Putting those 10 people on Team Members at USD 8 would add USD 80 per month and still would not match a full receive-and-pick day. Premium for all 25, at USD 110, would be USD 2,750 per month. Pay that only if those users need service or manufacturing.

On Odoo, if an outside EDI or 3PL system must call the API, use Custom. At the discounted USD 61.00, 25 users is USD 1,525 per month during the 12-month discount window. At the USD 76.20 figure shown beside it, the same 25 users is USD 1,905 per month. Ten Light Users at USD 8.90 add USD 89 per month if those people qualify as barcode operators and an advisor quote includes them. Portal customers who only place orders add USD 0. Hosting on Odoo.sh, if you need custom code, is extra. After month 12, re-price the initial users at the undiscounted rate before you compare the stack with Business Central.

What EDI costs per trading partner

EDI cost is a monthly partner count plus a one-time mapping, and the mapping is where projects slip. A Canadian operator starting from a small wholesale base wrote that they were "New-ish to all things EDI and wholesale oriented business tech stacks" and were "Looking for solutions as we grow and update our tech stack." Those lines are from a Canadian EDI thread. The useful move is to separate web forms, an integrated API, and labels, then ask each retailer which of the three they will accept.

Orderful's published list, as of October 2026:

• Web EDI Fulfillment (List price: USD 189 per month per trading partner · What you are buying: Browser fulfillment for that partner)
• Integrated API (List price: Starting at USD 399 per month · What you are buying: API EDI, starting price)
• UCC-128 labels (List price: Starting at USD 99 per month · What you are buying: Retail-compliant labels)
• Enterprise (List price: Custom quote · What you are buying: More than 20 trading partners)

Channels listed are AS2, SFTP/FTP, and VAN. Standards listed are X12 and EDIFACT. Source: Orderful pricing. Take the partner's routing guide as the spec. A public rate card cannot tell you whether that buyer wants a label, a particular envelope, or a test cycle that takes six weeks of their calendar.

Assume 6 trading partners on web EDI. Web EDI at USD 189 is USD 1,134 per month, or USD 13,608 per year, before labels. The UCC-128 figure of USD 99 per month is a starting price until the quote says whether it is per account or per partner. If it is per partner, six partners are 6 times USD 99, or USD 594 per month. An integrated API at the USD 399 starting price is USD 4,788 per year before any overage the quote adds. Twenty partners on web EDI are 20 times USD 189, or USD 3,780 per month, still on the published web EDI card. The custom Enterprise quote replaces that card once the count is more than 20. Get that quote before you sign the twenty-first partner.

Business Central's e-document framework is a different product decision. It handles electronic invoices and related documents. The default format choice is PEPPOL BIS 3 or a Data Exchange definition. With no connector installed, Service Integration is "No integration." Clearance-model examples on the e-documents setup page are Spain, India, Mexico, and Italy. The United States and Canada are absent from that clearance-model list. Keep PEPPOL e-invoicing and retailer EDI in separate budget lines.

Budget retail EDI as an external connection, and expect the Custom plan if that connection calls Odoo's API.

One European Business Central practice, Asio Services, prices each extra connector, including EDI, at about EUR 5,000 to 30,000, depending on protocol and volume. That is a services estimate from that firm, in euros. It is separate from Microsoft's license list and from a US or Canadian project award. See their 2026 cost note. Use it to remember that the USD 189 subscription is the network fee. The map from their item number to your item number, and from their unit of measure to your unit of measure, is a project.

Why a stack of point tools gets expensive

QuickBooks for the books, a warehouse app for the bins, a web EDI portal for one retailer, and a spreadsheet for the exceptions: each piece can look cheap on its own monthly invoice. The cost shows up as repeated mappings. Every new tool learns the item and the unit of measure again. A short-ship then needs a human who knows which of the three quantities is the one finance will bill.

Here is the bill for the assumption above, licenses and EDI only, US list prices as of October 2026, before implementation hours.

• 25 Business Central Essentials users at USD 80 (Monthly: USD 2,000 · Yearly: USD 24,000)
• 6 trading partners on Orderful web EDI at USD 189 (Monthly: USD 1,134 · Yearly: USD 13,608)
• Licenses plus web EDI (Monthly: USD 3,134 · Yearly: USD 37,608)

UCC-128 labels stay out of that total. USD 99 is a starting price until the quote says per account or per partner. If the starting price is per partner, six partners are USD 594 per month on top of USD 3,134. That table also leaves out Device licenses, connector hours, and Odoo.sh if you leave Business Central. Swap the ERP line for Odoo Custom at the discounted USD 61.00 and the 25 users become USD 1,525 per month, plus USD 89 if ten barcode operators are Light Users, and you still add the USD 1,134 EDI line if Orderful, or any outside system, is calling in. A lower ERP line leaves the EDI line where it is. The EDI line moves when you drop a partner or leave web forms.

A second failure mode is the portal bolted on beside EDI with no rule for who wins. The same Canadian EDI thread says, "We operate a small warehouse and sell via our Shopify store, have 150 small independent retailers." At that count, some retailers will order on a portal and a few larger ones will eventually demand documents. Decide, per customer, which channel creates the sales order. If both the portal and the EDI file can create an order for the same account, you will ship twice or spend Friday deleting duplicates.

What changes for a Canadian wholesaler

Canada uses the same stack order, with its own tax setup, bank files, and list prices.

On the Canadian Business Central pricing page, Essentials is CAD 108.50 per user per month, Premium is CAD 149.20, and Team Members is CAD 10.90, each paid yearly and each plus applicable tax. Using the same 25 full users, Essentials is CAD 2,712.50 per month before tax, or CAD 32,550 per year before tax. Premium for those 25 is CAD 3,730 per month before tax. Team Members at CAD 10.90 remain a light-access license, not a picker license.

The Canadian local functionality in Business Central documents sales tax and GST reporting, unrealized sales tax, use tax and purchase tax, deposits, electronic bank-file payments, and GIFI codes. Have your accountant walk a real invoice from a customer in another province through that setup, including a use-tax case, before you treat the localization as finished. Retail EDI is still a separate connector. Bank-file payments on that page are not the same thing as a named EDI payment document from a retailer.

Odoo 19's Canada localization installs Canadian accounting reports and Canadian check printing. Default fiscal positions cover every province and territory plus International. Odoo states that when the vendor delivers, tax follows the customer's province, and that Avalara AvaTax can be integrated for Canada and the United States. Vendor EFT uses a CPA005 file through the payment module described on the Canada fiscal localization page. Run one invoice per province you ship to, and one EFT file your bank will accept, on a test company. A fiscal position on a list is not a filed return.

EDI list prices from Orderful are in USD even when you operate in Canada. Put the foreign-exchange assumption in the purchase order to the EDI vendor so finance is not surprised in month two.

What implementation costs besides the licenses

Microsoft does not publish an implementation price for Business Central. The license table is the part you can audit from a public page. The project is whatever scope you sign.

Odoo publishes Success Pack hours because subscription plans exclude implementation services. Companies under 50 employees are directed to Odoo Success Packs. Companies over 50 employees are directed to a local partner. A 40-person wholesaler is in the pack path. A 70-person wholesaler is in the partner path. Many firms in the 30 to 100 range will cross that line during the project, so ask which path the quote assumes if you hire in the same year.

Success Packs for new customers, with a 15 percent discount on the first pack, as of October 2026:

• Starter (Hours: 4 · New-customer price: USD 493 · Price before that discount: USD 580)
• Basic (Hours: 25 · New-customer price: USD 3,060 · Price before that discount: USD 3,600)
• Standard (Hours: 50 · New-customer price: USD 5,950 · Price before that discount: USD 7,000)
• Custom (Hours: 100 · New-customer price: USD 10,625 · Price before that discount: USD 12,500)
• Pro (Hours: 200 · New-customer price: USD 21,250 · Price before that discount: USD 25,000)

Onsite travel is extra. Extra monthly charges apply for maintenance of extra modules. Source: Odoo Success Packs. The Standard pack is 50 hours at USD 5,950 for a new customer. Odoo publishes the hours and the price. The bidder has to show whether the chart of accounts, items, one warehouse, partner maps, a 3PL, and a portal fit inside the hours purchased. Two hundred hours at USD 21,250 is the largest pack on that page. If your item master, open orders, and partner testing need more than that, the pack is a start, not the project.

Asio Services published 2026 Business Central ranges in euros: about EUR 50,000 to 120,000 for 10 to 30 users with simple processes, EUR 120,000 to 350,000 for 30 to 150 users, and EUR 350,000 to 1,500,000 for complex multi-entity work. Those are that firm's figures for its own projects. Leave them in euros. They sit apart from Microsoft list prices and from a US or Canadian project award. A 30 to 100 person headcount does not select the middle band. Your number moves with entity count, warehouse level, and how many connectors you put in phase one. Asio Services also estimates each extra connector, including EDI, at about EUR 5,000 to 30,000. That connector estimate stays in euros and is separate from a US or Canadian award. Tell each bidder to price every connector as its own line in the currency that bidder bills.

Ask each bidder to price these as separate lines: data migration, warehouse configuration level, each trading partner, labels, portal, and training for the people who scan. A single blended fee makes the second partner look free until change-control pricing arrives.

How to phase the work and who should own the map

Phase one is the ERP plus the warehouse rung the building needs at go-live, with items, customers, open purchase orders, on-hand quantity, and costing reconciled to the last closed month. Phase two is the first trading partners who have a written document list, plus labels if their guide requires them. Phase three is the portal for the long tail of retailers who will keep emailing spreadsheets, and any separate WMS you still need after the ERP warehouse has been live long enough to judge it.

Our target for a first usable phase is 8 to 12 weeks, using the Flectic Accelerated Delivery Framework: a fixed scope, a named consultant reviewing the configuration, and a go-live limited to the workflows in that scope. That target is ours, and it assumes the phase is small enough to fit. Six EDI partners plus a directed warehouse in the first phase will not fit it. Cut the phase before you cut the test.

Before you sign, name the people who will configure the system, the hours they will spend on your company, two reference wholesalers with a similar warehouse level, the phase plan with a content list, and who owns the code and the item mappings if the project stops. If a bidder will not show those five, the proposal is still a license quote.

For distributors, we scope that sequence on our wholesale distribution work: finance and inventory first, warehouse documents at the rung you will use, EDI as named partners, portal when the order channel is clear. Where the hard part is the movement of goods, the same phase plan sits inside supply chain implementation. Teams that already know they want Business Central can start from Business Central for growing companies and still keep EDI and any later WMS as later phases.

Bring a partner count, a user list by role, and one ugly spreadsheet of items to the call. Those three inputs price the stack faster than a feature checklist.

How Flectic can help

Flectic brings pricing, multi-warehouse inventory and finance together on Dynamics 365 or Odoo for distributors of 20 to 100 people in the US and Canada. Flectic sends a written proposal with a fixed price for each phase before work starts. If a stack of point tools is holding back your orders, see wholesale and distribution ERP for how we fit the ERP layer. Book a free discovery call with Flectic to decide which layer to replace first.

Sources

Distribution software, Wikipedia, October 2026.

Dynamics 365 Business Central pricing (United States), Microsoft, October 2026.

Dynamics 365 Business Central pricing (Canada), Microsoft, October 2026.

Licensing in Business Central, Microsoft Learn, October 2026.

Manage warehouse activities, Microsoft Learn, October 2026.

Set up e-documents, Microsoft Learn, October 2026.

Canada local functionality, Microsoft Learn, October 2026.

Odoo Pricing, Odoo, October 2026.

Odoo Success Packs, Odoo, October 2026.

Odoo Inventory features, Odoo, October 2026.

Canada fiscal localization, Odoo, October 2026.

Orderful pricing, Orderful, October 2026.

Business Central implementation cost in 2026, Asio Services, October 2026.

CRM/ERP software for a growing wholesale business, Reddit, accessed October 2026.

Looking for solutions as we grow and update our tech stack, Reddit, accessed October 2026.