ERP for the auto industry: dealers, parts makers and suppliers

Auto industry ERP is three different buys. A Tier 2 or Tier 3 parts plant needs production orders, lot genealogy, and a path for OEM documents. An aftermarket distributor needs catalogue depth and warehouse control. A dealer group keeps its franchise dealer management system and uses ERP only where that system stops. Manufacturing on Dynamics 365 Business Central is on Premium at USD 110 per user per month, paid yearly, as of October 2026. OEM electronic data interchange is a separate project on Business Central and on Odoo.

On a 25-user plant with every person on a full licence, Premium is USD 2,750 per month. Odoo Custom, as of October 2026, lists USD 61.00 and USD 76.20 per user per month, about USD 1,525 to USD 1,905. EDI maps and label work sit outside both subscriptions.

Which of the three auto buyers you are

A company of 20 to 100 people is usually one of three buyers, and each buyer can leave a large part of a full automotive suite unused.

A Tier 2 or Tier 3 parts maker ships to an OEM or to a larger supplier. The daily pressure is a release that moves, a lot an auditor can walk backward, and an outside process such as heat treat or plating. AIAG's supply-chain training lists electronic data interchange next to transportation and inventory as day-to-day operational control. This buyer cannot skip lot identity or the document list the customer already sends. This buyer can skip a dealer-management conversation and, unless the customer requires it, a just-in-sequence broadcast.

An aftermarket distributor sells replacement parts across many vehicle applications. Captivea describes "catalogues of tens of thousands of references, cross-referenced by model". The work is search, supersession, multi-step returns, and stock in more than one building. A full production routing is optional if you buy finished goods. OEM release EDI is optional if your customers order by purchase order.

A dealer group runs franchise stores. Those stores already sit on a dealer management system the manufacturer named. List prices for those systems are a quote from the DMS vendor. The ERP question is the rest of the group: a wholesale parts arm, a non-franchise shop, or the company close. Have the bidder draw that boundary on your legal entities before anyone prices manufacturing seats.

SoftwareConnect's July 2026 roundup uses its own product sort and leaves dealer groups out: QAD for tiered suppliers, SYSPRO for OEM suppliers, DELMIAWorks for parts plants, Acumatica for parts distribution, Epicor Vision for aftermarket, Infor for specialty vehicles, and SAP Cloud ERP for large OEMs. Specialty vehicles and large OEMs are extra segments on that page. QAD and SAP Cloud ERP are labels on the roundup, and the page shows no public starting price for them. Business Central and Odoo are absent, and where the page prints prices it prints reviewer estimates. For a wider pass at how industries split systems, see our ERP examples by industry.

What IATF 16949 requires from the plant

On 3 October 2016 the International Automotive Task Force published IATF 16949:2016, replacing ISO/TS 16949, according to AIAG. AIAG describes the manual, together with customer-specific requirements, as the quality management system for automotive production, service, and accessory parts, implemented with ISO 9001:2015. The certificate is issued to the plant by an IATF-recognized certification body.

AIAG sells the English hard copy and the single-user e-document (product IATF-1) at USD 60 for members and USD 177 for non-members, as of October 2026. Buy the standard and read the clauses your customers cite. An ERP subscription does not include that reading.

AIAG's lead-auditor course focuses on IATF 16949:2016 and customer-specific requirements for Stellantis, Ford, and General Motors. The same AIAG page says core-tools auditing is a required competency under the IATF scheme, and that the core-tools course covers six core tools. Your quality manager still owns the audit. The system stores the records the auditor asks to see: lots, inspection results, and nonconformance history.

Wikipedia, citing the IATF scheme, says a certificate is valid for three years and must be confirmed at least annually by an auditor from an IATF-recognized certification body. Put the certificate date and the next surveillance visit on the project calendar. A go-live that lands in the month before surveillance is a bad month to discover that lot history stopped at the receiving dock.

Odoo Quality and Dynamics 365 Supply Chain Management can hold inspection evidence. The certificate still belongs to the plant, issued by an IATF-recognized certification body. In the pilot, ask which record, on which screen, supports the clause your customer cited.

Lot trace from the component lot to the customer

Business Central item tracking covers serial, lot, and package numbers on inbound and outbound documents, with item ledger history. Item Tracing can run Usage to Origin or Origin to Usage and can include components. Microsoft positions that path for recalls, warranties, and finding which customers received a lot. The production-order articles do not state that item tracking requires Premium. What the US pricing page does state is that manufacturing sits on Premium, described as Essentials plus service management and manufacturing. Essentials is USD 80 per user per month, paid yearly, as of October 2026. A parts plant that will issue production orders should price Premium, then confirm on a trial company which tracking fields a Team Member can post.

Odoo documents lots and serial numbers as optional traceability, turned on in settings, with a lots and serial numbers screen and a traceability smart button covering receipts, storage, and shipments. Odoo also describes upstream and downstream traceability of components, lots, and serials as a manufacturing feature. Turn the setting on during the pilot and run one finished lot backward to components and forward to a shipment before you train the floor. If the button is empty, the process never captured the lot, and a later audit will show the same gap.

The floor habit matters more than the screen. If receivers still write the heat number on a traveler and never scan it, both products will show a clean ship confirm and a broken genealogy. Ask for a receiving script, a production consumption script, and a ship script, each with a reject path when the lot is missing.

Quality records split by product, and the split changes the seat budget. Dynamics 365 Supply Chain Management documents quality orders, item sampling, acceptable quality level, quarantine-style blocking, certificates of analysis, and nonconformance types (customer, service request, vendor, production, internal, and co-product), with problem types and correction tasks. That product is USD 210 per user per month, and Supply Chain Management Premium is USD 300, both paid yearly, as of October 2026. The Business Central production-order articles describe BOMs, routings, flushing, and order statuses. They do not describe those quality orders. Price Supply Chain Management for the roles that need that record, and have the licence rules confirmed on your agreement before you assume every user moves.

Odoo 19 Quality is a separate app that creates quality checks, control points, alerts, and failure locations. Documented check types include instructions, pass-fail, measure, and take a picture. The manufacturing app also advertises shop-floor quality tests and statistical analysis of quality issues. For a plant whose incoming inspection is a pass-fail and a photo, that app is the feature to test. For a customer that wants sampling plans, certificates of analysis, and typed correction tasks inside the Microsoft quality model, put Supply Chain Management on the shortlist and compare the seat count with the record that customer expects to see.

Licence versus a separate EDI and label project

Infor's automotive page says CloudSuite Automotive supports multi-mode manufacturing (job shop, repetitive, and project), JIT and JIS assembly sequencing, and EDI-integrated trading-partner collaboration, and that its PLM supports APQP and MMOG. That is what a purpose-built suite claims in public. Have each Business Central or Odoo bidder show planning releases, advance ship notices, invoices, and any just-in-sequence broadcast on your tenant, or price a translator and a map as a separate line.

SoftwareConnect puts the same warning in buyer language: "3rd party add-ons may be necessary, like EDI and shipping notifications". AIAG publishes a Global DELJIT message guideline, product E-12, as a joint AIAG, JAMA/JAPIA, and Odette document for the UN/EDIFACT DELJIT message. If a customer cites DELJIT, the translator and the map are project scope. Ask each bidder to price data migration, the EDI document list, and label compliance as their own lines.

On Odoo, the external API is a Custom-plan feature. The Standard plan is Odoo Online only. Custom adds Odoo.sh or on-premise, Odoo Studio, multi-company, and the external API. Odoo.sh hosting and implementation services sit outside the subscription. A plant that will connect a translator should price Custom. A plant that will keep EDI in a portal and re-key a short document list can price Standard and still test lots and quality checks.

• Production orders, BOMs, routings (In the product docs: Business Central Premium; Odoo Manufacturing · Treat as its own line: Pilot on your BOMs, including revision rules)
• Lot and serial genealogy (In the product docs: Business Central item tracing; Odoo traceability · Treat as its own line: Floor scanning and the reject path when a lot is missing)
• Incoming checks and alerts (In the product docs: Odoo Quality app · Treat as its own line: IATF clauses, control plans, and customer-specific forms)
• Sampling, AQL, quality orders, nonconformance types (In the product docs: Dynamics 365 Supply Chain Management · Treat as its own line: Seat count, because this is a different licence)
• Subcontracted operations (In the product docs: Business Central work center, or the subcontracting extension; Odoo subcontracting BoMs · Treat as its own line: Lot identity while the part is off site)
• OEM releases, ASNs, invoices, DELJIT, labels (In the product docs: Show them on your tenant or price them separately · Treat as its own line: Translator, map, labels, and a retest when the customer changes version)
• JIT or JIS sequencing, APQP and MMOG in PLM (In the product docs: Claimed on Infor CloudSuite Automotive · Treat as its own line: Only if a customer requires that depth)

A Reddit poster looking at automotive ERP wrote, "We ended up looking at Epicor and Infor, and both had solid industry-specific features, especially for BOM management and supplier tracking". Industry features on a shortlist are a reason to demand a script on your data, and to keep the line-item split above on the quote.

What a 25-user parts plant pays each month

Assume 25 users, each needing a full licence, and no Team Member or Light User seats. Figures are list prices as of October 2026, before tax, implementation, EDI, and labels. The Canada Business Central page is included because some groups buy the Canadian tenant. Odoo figures below are the US page only.

• Business Central Essentials (US) (List price: USD 80 per user per month, paid yearly · 25 full users per month: USD 2,000, and manufacturing is not included)
• Business Central Premium (US) (List price: USD 110 per user per month, paid yearly · 25 full users per month: USD 2,750)
• Business Central Team Members (US) (List price: USD 8 per user per month, paid yearly · 25 full users per month: Not in the 25; use only for roles the agreement allows)
• Business Central Premium (Canada) (List price: CAD 149.20 per user per month, paid yearly, plus tax · 25 full users per month: CAD 3,730)
• Business Central Essentials (Canada) (List price: CAD 108.50 · 25 full users per month: CAD 2,712.50, without manufacturing)
• Supply Chain Management (US) (List price: USD 210 per user per month, paid yearly · 25 full users per month: USD 5,250 if all 25 seats move)
• Odoo Standard (US page, both figures) (List price: USD 31.10 and USD 38.90 per user per month · 25 full users per month: USD 777.50 to USD 972.50 on Odoo Online)
• Odoo Custom (US page, both figures) (List price: USD 61.00 and USD 76.20 per user per month · 25 full users per month: USD 1,525 to USD 1,905)

Sources for the table: Business Central US pricing, Business Central Canada pricing, Supply Chain Management US pricing, and Odoo pricing. Canada Supply Chain Management is CAD 284.90, and Supply Chain Management Premium is CAD 407.00, per user per month, paid yearly, plus tax, on the Canada SCM page. Odoo's footnote says the discount applies for 12 months to the initial users ordered. Read the order form to see which of the two figures you will be billed after month twelve.

Team Members at USD 8, or CAD 10.90 on the Canada page, can change the mix if shop-floor people only consume a narrow set of tasks. Have those tasks demonstrated. Odoo lists a Light User at USD 8.90, with shop-floor manufacturing use described as a light-user capability, sold through an advisor quote. Until that quote names your screens, keep Light Users out of the comparison.

Odoo Success Packs, for new customers, as of October 2026: Starter USD 493 for 4 hours, Basic USD 3,060 for 25 hours, Standard USD 5,950 for 50 hours, Custom USD 10,625 for 100 hours, and Pro USD 21,250 for 200 hours. Returning-customer prices run from Starter USD 580 through Pro USD 25,000. The 15 percent new-customer discount applies to the first pack only. Odoo says 80 percent of projects in the estimator's scope go live in 200 hours or less, and that companies above 50 employees usually use a partner. Those packs are hours of consulting. OEM maps and the rest of an automotive go-live sit outside that hour count.

For this 25-user, single-entity parts plant, Business Central Premium is the Microsoft licence that includes manufacturing, at USD 2,750 per month. Choose Odoo Custom when you need the external API or multi-company and you accept a separate services budget. Choose Supply Chain Management when you need that product's quality orders, sampling, and nonconformance records. A side-by-side of those tradeoffs sits on our ERP comparison matrix.

Subcontracted operations without losing the lot

Heat treat, plating, and outside machining are normal in a small automotive machine shop. The failure mode is a lot that leaves as one identity and returns as a quantity with no lot, then ships to the customer anyway.

Business Central can subcontract a routing operation to a vendor with a vendor-linked work center and no extra app. A separate Microsoft-published Subcontracting extension adds a subcontracting worksheet, purchase orders from production orders, component resupply, and item charges. Decide in the pilot which of the two you will use. The work center covers the routing step. The extension is the one that adds the worksheet and the purchase document tied to the production order. Either way, require the vendor shipment and the return receipt to carry the same lot or a recorded child lot.

Odoo 19 documents three subcontracting workflows once the setting is on: basic (the subcontractor buys components), resupply subcontractor on order, and dropship to subcontractor. A subcontracting BoM type marks the product as made by the vendor. Run the workflow you will use in production, with a scrap quantity, before you call the design done. Use resupply when you own the blank and need it back under your lot. Use basic or dropship only when that is how the vendor buys or receives the part.

Production orders in Business Central use the statuses Simulated, Planned, Firm Planned, Released, and Finished. They are built from items, production BOMs, routings, and work or machine centers, and they can be fed by the planning worksheet, sales-order planning, or order planning. Forward, backward, and manual flushing post component consumption and output. There is no dedicated by-product feature. By-products post as a negative consumption journal line. If your process creates a recoverable drop, script that negative line with the quality lead present so the lot ledger still balances. How those BOMs and routings are set up is covered in Business Central manufacturing BOMs and routing, and how Business Central fits manufacturers walks the same fit for a general plant.

Captivea also describes "one-off builds where the design changes faster than the bill of material". If that is your shop, write the revision rule before go-live: who may change a BOM after a firm planned order exists, and which revision the lot stores. A simulated order is the place to test a design change. A released order is a poor place to discover the router is editing the live BOM.

Aftermarket distributors and dealer groups

Aftermarket work fails in the catalogue, the return, and the warehouse, more often than in a routing. Load a few thousand of your own references, including supersessions and a duplicate interchange, and time the search. Use your synonyms, because a vendor demo catalogue will not contain them. Returns need a disposition: restock, scrap, or send back to your supplier, with the lot or serial when you sell safety parts.

You can skip Premium manufacturing if you do not build. Business Central Essentials at USD 80, or Odoo Standard if you stay on Odoo Online and do not need the external API, is the pair to price first. Add Custom or an integration line only for the trading partners who will not stay on a portal. SoftwareConnect places Acumatica with parts distribution, and the reviewer range for Acumatica is in the table below. Epicor Vision, like QAD, Infor CloudSuite Automotive, and SAP Cloud ERP, has no public starting price on that roundup. Ask those vendors for a quote on your SKU count. The Epicor Kinetic row further down is a different product, priced there as a monthly reviewer estimate.

Dealer groups should keep the franchise dealer management system. A general ERP is the wrong place to recreate OEM warranty, vehicle inventory, and the manufacturer interfaces a franchise store already runs. Use ERP where the DMS stops: a separate wholesale company, a non-franchise location, or consolidation into the financial close. If a proposal says one database will run the showroom and the tier plant, split the proposal. The showroom and the plant do not share a first phase.

Our manufacturing implementation work is aimed at the plant and the parts warehouse in this range, phased so finance and inventory can go live while EDI maps are still in test. Business Central implementation and Odoo implementation use the same phase idea: configuration, data migration, training, and support after go-live, with customer documents scoped on their own.

How to choose the people who configure it

Partner badges are a sales sort. The tests that decide a 20 to 100 person auto project are the named people, the hours, the references, the phase plan, and who owns the code and the EDI maps after go-live.

Ask for the person who will design the lot path and the person who will sit with receiving. If those names are missing, the hours on the quote are a pool, and a pool drifts into your busiest release week. Ask for two references of similar headcount whose go-live included inventory lots. A reference that only closed the general ledger has not proven genealogy.

Put the first phase in writing: companies, sites, item masters, open orders, and the documents that are in. Put OEM EDI, label compliance, and historical lot backfill out, unless a customer deadline forces one document into phase one. Our target for a first usable phase is 8 to 12 weeks. That target assumes a bounded scope, a named internal owner, and data your team can extract. It is a planning target, and your EDI maps will move it if you pull them forward.

Odoo is explicit that implementation is extra and that firms above 50 employees usually use a partner. Business Central licence pages publish the subscription. The project fee belongs on the statement of work. In both cases the statement of work is the price that protects the audit. Compare that document, then use the fit answers from this page so the call starts from your lot path and your document list.

What specialty suites and reviewer lists charge

Infor's automotive page is the source here for multi-mode manufacturing (job shop, repetitive, and project), JIT and JIS assembly sequencing, and EDI-integrated trading-partner collaboration. That page does not publish a starting licence. SoftwareConnect labels QAD for tiered suppliers and SAP Cloud ERP for large OEMs, and the roundup shows no public starting price for QAD, Infor CloudSuite Automotive, Epicor Vision, or SAP Cloud ERP. Where the roundup does print numbers, it labels reviewer estimates, and the same page disagrees with itself.

• DELMIAWorks (Figure SoftwareConnect prints: About USD 250 per user per month, minimum five users · How to read it: Reviewer estimate, not a vendor price page)
• SYSPRO (Figure SoftwareConnect prints: USD 199 per user per month in the pricing table, and USD 150 on a product card on the same page · How to read it: Conflicting reviewer estimates)
• Epicor Kinetic (Figure SoftwareConnect prints: USD 2,100 per month · How to read it: Reviewer estimate, not a per-user price)
• Acumatica (Figure SoftwareConnect prints: A range running about USD 1,800 to USD 6,500 per month, with an average and a table that also cite USD 2,800 · How to read it: Reviewer estimates that depend on which sentence you use)

Source: SoftwareConnect, 7 July 2026. Treat the column as a reason to request a vendor quote, especially if a board member arrives with a specialty-suite budget. For a 25-user Tier 3 plant, compare that quote with Business Central Premium at USD 2,750 per month plus an EDI line, or with Odoo Custom at about USD 1,525 to USD 1,905 per month plus a Success Pack and the same EDI line. The suite wins when a customer requires JIS sequencing or the PLM depth Infor describes. The mid-market licence wins when your gap is lots, subcontract steps, and a finite document list you are willing to buy as a project.

How Flectic can help

For parts makers and suppliers of 20 to 100 people in the US and Canada, Flectic connects production, inventory and finance on Dynamics 365 or Odoo, so your schedule, your costing and your order book agree. Lot traceability in our manufacturing ERP work gives genealogy from raw lot to finished serial, so a recall is scoped from system records. Flectic sends a written proposal with a fixed price for each phase before work starts. To check whether lot trace and your customer documents fit your plant, select Book a free discovery call and Flectic will go through them with you.

Sources

• Dynamics 365 Business Central pricing (United States), Microsoft, October 2026
• Dynamics 365 Business Central pricing (Canada), Microsoft, October 2026
• Dynamics 365 Supply Chain Management pricing (United States), Microsoft, October 2026
• Dynamics 365 Supply Chain Management pricing (Canada), Microsoft, October 2026
• About production orders, Microsoft Learn, October 2026
• Trace item-tracked items, Microsoft Learn, October 2026
• Subcontract manufacturing, Microsoft Learn, October 2026
• Quality and nonconformance management, Microsoft Learn, October 2026
• Odoo pricing, Odoo, October 2026
• Odoo Success Packs, Odoo, October 2026
• Odoo 19 product tracking, Odoo, October 2026
• Odoo 19 Quality, Odoo, October 2026
• Odoo 19 Subcontracting, Odoo, October 2026
• IATF 16949:2016, AIAG, October 2026
• Supply Chain Management, AIAG, October 2026
• IATF 16949, Wikipedia, October 2026
• Automotive ERP Software, Infor, October 2026
• Top 7 Automotive ERP Software on the Market in 2026, SoftwareConnect, July 2026
• Transform your automotive industry, Captivea, October 2026
• ERP recommendation for automotive industry, Reddit, September 2025