ERP for manufacturing industry: auto, electronics, and Industry 4.0
Manufacturing ERP, for a discrete plant, is one system for multi-level bills of materials, production orders, inventory, and cost.
Manufacturing ERP, for a discrete plant, is one system for multi-level bills of materials, production orders, inventory, and cost. Automotive suppliers and electronics assemblers then pass or fail that system on lot genealogy and customer releases. If you run production in Business Central, budget the Premium licence: USD 110.00 per user per month in the United States, or CAD 149.20 per user per month in Canada, paid yearly, plus applicable tax, as of October 2026. Essentials, listed at USD 80.00 and CAD 108.50 per user per month, paid yearly, does not include manufacturing, and an Essentials user cannot sign in to a Premium company. On a plant of about 50 people, certify bills, routings, and lots now, and leave a separate MES for a later phase.
That is a different buying job from a generic ERP definition. Directories still sort products by a feature grid and, in at least one 2026 roundup, quote a Business Central user price that does not match Microsoft's list. The pages below separate what a 30 to 100 person plant can run inside Odoo or Business Central from what has to live in an EDI translator, a quality file, or a later machine connection. For the planning mechanics under those choices, our manufacturing ERP fundamentals covers MRP, routing, and costing. This page stays on sub-industry proof and how connected the floor needs to be.
What a discrete plant should expect manufacturing ERP to post
A useful system creates a production order from a bill and a routing, consumes components, records output, and leaves a cost and a lot trail a buyer can reopen. Both products we implement do that core. They do it with different paperwork.
In Business Central, manufacturing sits in the Premium experience: production BOMs, routings, work and machine centers, and production orders. Microsoft documents that only Evaluation or Premium licences can switch the company from Essentials to Premium, and that an Essentials user cannot sign in once that switch is made. Order statuses run Simulated, Planned, Firm Planned, Released, and Finished. Consumption and output can be posted by hand or by forward or backward flushing. A by-product is not its own feature. Microsoft's production-order page documents it as a negative consumption entry, so scrap recovery and a true co-product need a tested posting pattern before you promise it to finance.
Bills are where electronics and automotive work either holds or falls apart. Business Central builds multi-level structures by placing a certified production BOM on a component line. A phantom BOM explodes into the parent order without its own production order, which is the right shape for a kit that never sits in stock. Versions carry a Version Code and a Starting Date, and a version stays valid until the next version's starting date. The Production BOM Version Comparison page compares quantities across versions. That is dated, certified revision control. It is not an engineering-change workflow with an approval gate.
Odoo Manufacturing sells MRP, MES, PLM, Quality, shop floor, and maintenance as one suite: multi-level planning, finite-capacity Gantt scheduling, a master production schedule, lot and serial traceability, by-products, and an IoT box. Work orders are a setting, so a plant can start with manufacturing orders and turn work orders on when the routing is stable. Shop-floor instructions that go past a worksheet require the Quality app. Components are products that can carry their own bills, so a multi-level BOM is a chain of products. A component can be tied to an operation. Flexible consumption can be allowed or blocked. With PLM installed, the bill has a Version field. By-products appear after that setting is on.
A single-entity plant can run make-to-stock or a short configure-to-order flow on either product when the bill is certified and the lot or serial rule is mandatory on receipt. The failure mode in a feature-grid shortlist is buying that core, then discovering the customer release file and the revision gate were never in the demo script.
What automotive tier suppliers have to prove
IATF 16949:2016 replaced ISO/TS 16949 in October 2016. It is an automotive quality-management system built on ISO 9001, and it cannot stand alone. It applies to sites that make customer-specified production parts, service parts, and accessory parts. A certificate lasts three years, with at least an annual audit. Customer-specific requirements sit on top of the standard. The core tools named with the standard are APQP, PPAP, FMEA, MSA, and SPC. Design and development may be excluded when the organization does not own product design. Manufacturing process design may not be excluded. If you are a tier supplier, the auditor will look at process control even when the OEM owns the print.
The quality system still lives with the site. The ERP has to hold the records that system points at: which lot or serial went into which shipment, which operation recorded a check, and where the PPAP file for that part revision lives. Business Central and Odoo production pages do not describe a PPAP packet generator or an IATF control-plan module. Plan a controlled folder, a quality app, or an add-on, and make a bidder open last month's PPAP on your part number during the demo. Ask them to show the lot genealogy from the same shipment without leaving the item ledger or the traceability report.
Customer demand arrives as EDI. When the customer uses the 830 as the release, a separate purchase order is often unnecessary.
How an 830 planning release differs from an 862 ship schedule
The X12 830 Planning Schedule with Release Capability is a forecast a manufacturer typically sends a supplier. 1 EDI Source describes three uses: a forecast alone, "a forecast with the buyer's authorization for the seller to commit to resources, such as labor or material", or a forecast that also releases orders, including cumulatives and weekly, monthly, or quarterly buckets. The same page says "the order release capability eliminates the need for discrete generation of purchase orders" when the 830 is used as a release. The 862 Shipping Schedule is the transaction for actual shipping instructions.
Treat those as two clocks. The 830 tells you what labor and material you may commit, often in weekly buckets and cumulatives. The 862 tells you what to ship. A plant that keys both into a spreadsheet will ship the wrong cumulative the week a release replaces a firm window. Neither Business Central nor Odoo includes a native 830 parser in the product pages that describe production, bills, and lot tracking. OEM releases usually land through an EDI translator or an ISV app that writes forecast lines, blanket releases, or sales orders into the ERP. Put that interface in the statement of work as its own line, with a sample 830 and 862 from your highest-volume customer. A feature checklist that says "EDI supported" hides whose map breaks when the cumulative resets.
Traceability is the other half of the same audit. Business Central assigns serial numbers, lot numbers, and package numbers on inbound and outbound documents, including purchase orders and transfer orders. Posted tracking sits on item ledger entries. Serial and lot information cards store a description, comments, and a Blocked flag. The mobile app can scan 1D and 2D barcodes into tracking fields. Odoo 19 tracks by lot or serial once Lots and Serial Numbers is on. A receipt cannot be validated without a lot or serial when the product requires it. The traceability report lists stock moves for a lot. Delivery slips can print lot and serial numbers. Removal can follow FIFO, LIFO, or FEFO. For an automotive ship-to, FEFO matters when date-sensitive material shares a bin with older stock. Turn the requirement on for purchased components and for the finished part, then run one recall question: given a customer claim on a serial, which component lots were issued to that order?
What electronics assemblers have to control on the bill
Electronics work fails on revision and on the reel, more often than on the routing screen. An electronics bill is multi-level: finished assembly, subassemblies, and components that are manufactured or purchased. Both products support that shape. Business Central nests a certified production BOM on a component line and compares quantities across dated versions. Odoo treats each component as a product with its own bill, and PLM adds a Version field.
Revision control is where they split. Odoo engineering change orders, in the PLM app, revise a bill or a product, assign the next version (V2, V3), and keep that revision off the production bill until someone uses Apply Changes. The change can take effect as soon as possible or on a date. BoM Changes and Operation Changes tabs show adds, updates, and removals. That is the control an assembler wants when a resistor value changes and open orders must stay on the old version until a date. Business Central's dated, certified versions and the comparison page give you history and a start date. Those production BOM pages do not describe an engineering-change order that stays off the production bill until someone applies it. If your process needs a requested, approved, and applied state, confirm whether you will run that in Odoo PLM, in a Business Central extension, or in a procedure outside the bill.
Component obsolescence is a process you still have to assign. Last-time-buy dates, approved alternates, date codes, and reel identity sit outside the standard bill, version, and lot tools described for both products. Ask each bidder to show, on your data, an alternate part, a last-time-buy date, and a reel or lot that can be blocked. If the answer is a spreadsheet beside the item card, price that spreadsheet as a process you will still run after go-live, or as an app with its own licence.
Reel and lot practice still uses the tracking both products do have. Receive the reel under a lot, block the lot when the date code is expired, and stop a delivery slip that would ship a finished serial without component lots. Odoo will refuse to validate the receipt when the product requires a lot. Business Central stores the lot on the item ledger and can block the lot card. Package numbers in Business Central are the extra handle when a carton holds many serials. None of that prints a date-code rule by itself. You still need a receiving check that a person, or a quality control point, performs.
What Business Central and Odoo cost for a plant this size
List price is the part a directory most often gets wrong. Top10ERP's 2026 manufacturing roundup lists Business Central at USD 175 per user per month. Microsoft's own pages, as of October 2026, list Essentials at USD 80.00 and Premium at USD 110.00, paid yearly. Use the publisher's page for the licence you will sign, and treat USD 175 as a directory figure that conflicts with that list. The same directory lists a minimum implementation fee of USD 35,000. That is Top10ERP's figure, not a Microsoft price list and not a quote for your EDI map.
- Business Central Essentials (United States: USD 80.00 per user per month, paid yearly · Canada: CAD 108.50 per user per month, paid yearly, plus tax · What it covers: Finance, sales, purchasing, inventory. No manufacturing experience.)
- Business Central Premium (United States: USD 110.00 per user per month, paid yearly · Canada: CAD 149.20 per user per month, paid yearly, plus tax · What it covers: Essentials plus service management and manufacturing. Required once the company uses the Premium experience.)
- Business Central Team Members (United States: USD 8.00 per user per month, paid yearly · Canada: CAD 10.90 per user per month, paid yearly, plus tax · What it covers: Limited read, approve, and selected updates. Not a shop-floor full user.)
- Odoo Standard (United States: USD 24.90 to USD 38.90 per user per month · Canada: No CAD price on Odoo's pricing page. · What it covers: All apps on Odoo Online, including manufacturing. Discount valid 12 months for the initial users ordered.)
- Odoo Custom (United States: USD 49.00 to USD 76.20 per user per month · Canada: No CAD price on Odoo's pricing page. · What it covers: Adds Odoo.sh, on-premise, Studio, multi-company, external API, and Odoo's agentic AI. Odoo.sh hosting is extra. Same 12-month discount note.)
- Odoo Light User (United States: USD 8.90 per Light User · Canada: No CAD price on Odoo's pricing page. · What it covers: Shop floor, inventory barcode operator, and the employee's own time off, expenses, and planning. Advisor quote, not self-serve checkout.)
United States and Canada Business Central amounts are Microsoft list prices as of October 2026 (US pricing, Canada pricing). Odoo amounts are the figures printed together on Odoo's pricing page as of October 2026. Odoo prints the yearly and monthly figures on the same pricing page, so the bands above are that printed range. A 30-day Business Central trial is free. Manufacturing in Odoo is inside the all-apps price, not a separate module fee.
A paying Odoo user is someone with backend create, view, or edit access, or an employee record with no linked user. Portal users such as customers and suppliers are not paying users. A Light User can run the Manufacturing shop floor. An engineer who edits bills is a full user. External API access, which an EDI translator or a machine gateway often needs, pushes the subscription to Custom, and Odoo.sh hosting is not included in that user price.
Assume a US plant with 18 people who create or edit finance, purchasing, and production orders, plus 22 people who only scan and report on the shop floor. Business Central manufacturing puts the company on Premium, and Essentials users cannot sign in, so you cannot keep planners on Premium and buyers on Essentials in that company. If all 40 people who sign in need full access, 40 times USD 110.00 times 12 is USD 52,800 per year before discounts. Team Members at USD 8.00 (USD 2,112 per year for those 22 people) is the wrong place to park operators, because that licence is not a shop-floor full user. If you confirm with Microsoft that a named role fits Team Members, price it on a role-by-role worksheet. Do not apply it to anyone who posts output.
On Odoo, the same 18 full users on Custom span USD 10,584 to USD 16,459.20 for a year at the printed monthly rates (18 times USD 49.00 times 12 up to 18 times USD 76.20 times 12). The 22 shop-floor people, if they qualify as Light Users, add USD 8.90 per Light User on top. Odoo's pricing page does not state the billing period for that rate, so ask for it in the advisor quote. Those totals sit before Odoo.sh hosting, before IoT boxes, and before the year-two price once the 12-month discount on initial users ends. Standard, at USD 24.90 to USD 38.90 per user per month, is only in range when you do not need the external API, multi-company, or Odoo.sh. A Canadian Business Central plant with the same 40 full users is 40 times CAD 149.20 times 12, which is CAD 71,616 per year plus tax, using the October 2026 Canada list. Keep Odoo quotes in US dollars until the order form shows a Canadian price.
Which Industry 4.0 pieces a 50-person plant needs now
Industry 4.0, for this size of discrete plant, is a sequence. A scorecard of MQTT brokers, digital twins, and a separate MES in the same purchase order as the first bills of material outruns the audit you can pass this year.
Now means four things you can demonstrate on a Tuesday:
- Certified production bills, with a version or engineering change that cannot leak onto a released order by accident.
- Routings and, when you are ready, work orders or work centers that record time and output against the order.
- Lot or serial numbers required on component receipts and on finished goods, with a report that walks from a shipment back to those lots.
- A quality check at the operation that matters, stored where the production record lives. In Odoo, instructions past a worksheet need the Quality app. In Business Central, have the implementer show the screen where inspection results sit on that production order.
Later means machine IoT as a plant historian, statistical process control charts, and a separate MES that schedules every minute of the cell. Those pieces pay when cycle-level data changes a release decision the same shift. They do not pay when the bill is still wrong and the 830 is still re-keyed. A 50-person automotive or electronics plant usually has one or two constraints that hurt this year: the wrong revision built, a lot you cannot find, or a ship schedule typed from a PDF. Fix those in the ERP. Add cell sensors when a named loss (a press, a reflow oven, a tester) is large enough that a person with a clipboard cannot see it.
Odoo sells a narrow step that sits between those two stages. The IoT box subscription is USD 30.00 per month per box as of October 2026. The box connects measurement tools, cameras, printers, and footswitches by Wi-Fi, Bluetooth, USB, or HDMI, and it can attach readings to quality control points. It supports Raspberry Pi 3 and 4 boxes. Ask for the device purchase price before you count boxes. One box on a caliper and a label printer is a practical Industry 4.0 step. A line historian is a later project, and the box still depends on the lot rule. Business Central can take barcode scans into tracking fields through the mobile app. A stream of machine-condition events into maintenance work orders is a separate integration design. Script it only after posting, lots, and customer releases already work.
Score a shortlist only after this now-versus-later line is drawn. A row that assumes a full MES in phase one prices a plant you do not need yet.
Where a feature checklist hides the integration gap
The pattern in automotive and electronics shortlists is a long module grid: BOM, MRP, shop floor, quality. The grid can be true and still miss the file that runs the week. For a tier supplier, that file is the 830 and the 862. For an assembler, it is the engineering change that must stay off the floor until a date, plus the reel you have to block. The production, bill, lot, and pricing pages for Business Central and Odoo do not include a native 830 parser, a PPAP packet generator, IATF control plans, SPC, or electronics obsolescence and date-code tracking. A scorecard that marks those words "supported" still needs a demo on your file.
Budget the gap as its own workstream.
- Take one real 830 and one real 862 from your largest customer. Ask the bidder who maps them, which ERP document they create, and what happens to a cumulative when the OEM resets it.
- Take one engineering change that overlaps open orders. Ask which orders stay on the old version and which field blocks the new bill.
- Take one reel that should stay in the cage. Ask the system to refuse the issue. A comment on the item card is easy for a picker to miss.
- If the map needs an external API, Odoo Custom is the licence tier, and hosting is extra. If Business Central needs an ISV for EDI, put the ISV subscription and the sandbox test in the same phase as go-live. Leaving that map until after users are live means the team keeps typing releases by hand.
Point-to-point scripts between a translator, a label printer, and the ERP become brittle when each vendor updates on its own calendar. Name an owner for each map, and keep the maps in a repository your company can read. Code ownership matters more here than a partner-tier badge. The tests that decide a bidder are the named people on the project, the hours against each map, references who run a similar release, a phase plan that ships bills and lots before machine data, and a written statement of who owns the integration code after go-live.
What timeline and services numbers are safe to use
Odoo's pricing page answers "Where can I get implementation services, and how much does it cost?" by splitting the market: companies under 50 employees usually buy Success Packs from Odoo, and "Mid-size and large companies (>50 employees) usually work with a partner". Success Packs are not a substitute for a partner quote at 30 to 100 people, especially once you are over 50. Use them as a published hour scale, then get a statement of work.
Odoo lists the new-customer Starter pack at 4 hours for USD 493, Basic at 25 hours for USD 3,060, Standard at 50 hours for USD 5,950, Custom at 100 hours for USD 10,625, and Pro at 200 hours for USD 21,250, as of October 2026. Those amounts already include 15 percent off the first pack. Returning-customer prices are USD 580, USD 3,600, USD 7,000, USD 12,500, and USD 25,000. The manufacturing bundle inside the estimator is MRP, PLM, Quality, and Maintenance. The new-customer packs top out at 200 hours and USD 21,250, and Odoo says 80 percent of projects inside the estimator scope go to production in 200 hours or less. Onsite travel and expenses are extra. Custom-module maintenance is an extra monthly charge. An 830 map, a PPAP file structure, and reel rules sit outside that scope. They need hours from a partner, priced as lines you can drop if you defer them.
ERP Research, updated October 2026, publishes analyst estimates, not vendor quotes: Microsoft Dynamics 365 from USD 50 per user per month, typical contract USD 150,000 to USD 1,000,000 or more, implementation 6 to 14 months. That card describes Supply Chain manufacturing, not Business Central alone. Do not paste 6 to 14 months onto a Business Central plant. The same page is still useful as what buyers see online for other products in this band. SYSPRO is listed for 50 to 500 employees, from USD 75 per user per month, total contract value USD 50,000 to USD 250,000, go-live 3 to 6 months. QAD Adaptive is listed from USD 90 per user per month, total contract value USD 150,000 to USD 600,000, 5 to 10 months, with EDI-driven customer schedules and automotive quality themes. Global Shop Solutions is listed for small and midsize job shops at USD 30,000 to USD 150,000 and 2 to 5 months. Those ranges are ERP Research estimates for the products named on that card. Price Odoo or Business Central from a statement of work and the vendor list prices above.
Top10ERP aims its roundup at "small and midsize businesses implementing manufacturing ERP for the first time" and pairs that audience with the USD 175 Business Central figure and the USD 35,000 minimum fee. If a proposal copies either number, ask for the Microsoft price list and an hour build-up. Flectic sets the timeline for a first phase in the written scope, with a fixed price, before work starts. A first phase here is certified bills, inventory with lots, and production orders your team can post, with customer-release maps scheduled only when the sample files are in hand. The timeline moves when the 830, the revision gate, or a second site is in phase one.
A practical split for about 50 people:
- Phase one: items, certified multi-level bills, routings, inventory with mandatory lots or serials, purchasing, and production order posting. Quality checks at the one operation your customers already audit.
- Phase two: the EDI translator or ISV, tested on a real 830 and 862, plus engineering changes held off production until applied.
- Phase three: IoT box or barcode capture at a named station, then a separate MES only if phase one and two data is already trusted.
Flectic's manufacturing work is scoped in that order for US and Canadian plants. Licence cash from the worked example above is the subscription. Services are the hours against each phase. Ask for data migration, the EDI map, and custom maintenance as separate lines so a low licence price cannot hide them.
How to choose Odoo or Business Central for this plant
Choose on the records you must defend, then on the licence rule that record forces.
Business Central Premium fits a plant already living in Microsoft 365 that wants production orders, dated BOM versions, phantoms, and item-ledger lot, serial, and package tracking inside one company. Budget every full user at USD 110.00 or CAD 149.20 per user per month, paid yearly, as of October 2026. Plan EDI and PPAP filing as adjacent products. Have the implementer show flushing, a negative line if you need a by-product, and a version comparison on your bill. Our note on whether Business Central fits manufacturing goes further on shop-floor depth. The licence gate remains the one in this page: Essentials cannot sit inside a manufacturing company.
Odoo fits a plant that wants MRP, shop floor, PLM engineering changes, quality checks, and maintenance on one database, with operators on a Light User at USD 8.90 where the role qualifies. Budget Custom, USD 49.00 to USD 76.20 per full user per month in the printed October 2026 range, as soon as an external API, multi-company, Studio, or Odoo.sh is required. Add USD 30.00 per month per IoT box only for stations where a tool reading or a label is the bottleneck. Our note on whether Odoo fits manufacturing covers app boundaries. The commercial gate on this page is the partner path: above 50 employees, Odoo points you to a partner, and the 200-hour pack is the estimator scope.
A short demo script beats a 40-row grid.
- Certify a two-level bill, revise one component, and show that yesterday's released order did not pick up the new version.
- Receive a lot, issue it to a production order, finish a serial, and ship it. Then open the trace from the serial back to the lot in under five minutes.
- Load a sample 830 into whatever tool the bidder proposes, and show the ERP document it creates. If they cannot load your file, the line item is still open.
- Price the people: Premium or Custom for editors, and a written reason for every Team Member or Light User.
- Name the consultant who will configure bills, the hours for the EDI map, and who owns the code when the project ends.
An Odoo rollout and a Business Central rollout can both start from that script. The plant that skips step 3 buys a manufacturing module and keeps the spreadsheet that already runs the week.
How Flectic can help
Flectic implements Dynamics 365 or Odoo for manufacturers of 20 to 100 people, with finite scheduling, real-time WIP and lot traceability in one system. We pilot one cell, then expand, so one line goes live with its operators first while the rest of the plant keeps producing. Review the manufacturing ERP offer against your Industry 4.0 plan, then Book a free discovery call with Flectic.
Sources
- Dynamics 365 Business Central pricing (United States), Microsoft, October 2026
- Dynamics 365 Business Central pricing (Canada), Microsoft, October 2026
- Enable Premium features, Microsoft Learn, October 2026
- About production orders, Microsoft Learn, October 2026
- Create production BOMs, Microsoft Learn, October 2026
- Track items with serial, lot, and package numbers, Microsoft Learn, October 2026
- Odoo Pricing, Odoo, October 2026
- Odoo Success Packs, Odoo, October 2026
- Odoo Manufacturing, Odoo, October 2026
- Bill of materials configuration, Odoo 19.0, Odoo, October 2026
- Engineering change orders, Odoo 19.0, Odoo, October 2026
- Lot numbers, Odoo 19.0, Odoo, October 2026
- Odoo IoT, Odoo, October 2026
- IATF 16949, Wikipedia, October 2026
- EDI 830 Planning Schedule with Release Capability, 1 EDI Source, October 2026
- Best ERP for Manufacturing (2026), ERP Research, October 2026
- Why These are the Top 10 Manufacturing ERP Systems for 2026, Top10ERP, October 2026
Frequently asked questions
What is a Light User?
Odoo prices a Light User at USD 8.90. That seat can use the Manufacturing shop floor, act as an inventory barcode operator, and handle the employee's own time off, expenses, and planning. Someone who creates or edits bills, orders, or other backend records is a paying full user. Customers and suppliers on the portal are not paying users. Light Users are sold through an advisor quote.
Does Business Central manufacturing require Premium, and can Essentials users stay in that company?
Yes. Production BOMs, routings, work centers, and production orders are part of the Premium experience. Only an Evaluation or Premium licence can switch the company from Essentials to Premium. A user who holds only Essentials cannot sign in to that company. Budget full users at the Premium list price, USD 110.00 in the United States or CAD 149.20 in Canada, per user per month, paid yearly, as of October 2026.
How is an EDI 830 planning schedule different from an 862 shipping schedule?
An 830 is a planning schedule a customer typically sends a supplier. It may be only a forecast, a forecast that authorizes labor or material, or a forecast that also releases orders, including cumulatives and weekly, monthly, or quarterly buckets. An 862 carries the actual shipping instructions. When the 830 is the release, a separate purchase order is often unnecessary. The two files should not be typed into the same spreadsheet column.
What is a realistic implementation timeline for a 30 to 100 person discrete plant?
Odoo says companies above 50 employees usually work with a partner, and that 80 percent of projects inside its estimator scope go to production in 200 hours or less. That scope is MRP, PLM, Quality, and Maintenance, and the largest new-customer pack on the page is 200 hours at USD 21,250 before travel. Customer EDI and reel rules sit outside that pack. Published 6 to 14 month figures for Dynamics 365 describe a broader Supply Chain card, so they are the wrong calendar for a Business Central plant. Ask for a phase plan with hours on each integration.
Which Industry 4.0 pieces does a 50-person plant need now versus later?
Now is certified bills, routings, lot or serial capture on receipts and finished goods, and a quality check at the operation customers already audit. Later is a separate MES, statistical process control, and machine data used as a plant historian. An Odoo IoT box at USD 30 per month per box can attach a tool, camera, printer, or footswitch to a quality point. That is a station connection. It does not replace the lot rule or an EDI release map.
Where can I get implementation services, and how much does it cost?
Under 50 employees, Odoo usually sells Success Packs. Odoo lists the new-customer Standard pack at 50 hours for USD 5,950 and the Pro pack at 200 hours for USD 21,250, amounts that already include 15 percent off the first pack. Above 50 employees, Odoo says companies usually work with a partner, and the packs are not a substitute for that quote. Travel, custom-module maintenance, EDI mapping, and Odoo.sh hosting are extra. Ask every bidder to price data migration and customer releases as their own lines.