ERP for pharmaceutical company: licenses, lots, and records

For a plant of about 20 to 100 people, Business Central or Odoo can cover lot tracking, expiry dates, and first-expired-first-out picking. Manufacturing sits on Business Central Premium at USD 110 per user per month in the US, or CAD 149.20 in Canada, paid yearly, as of October 2026. Odoo Custom is listed at USD 61 per user per month on the 12-month discount, as of October 2026. Move to a specialist pharma system when you need package-level tracing for certain US prescription drugs, or an electronic batch record that replaces signed paper. Lot and expiry control alone does not require that step.

The rest of this page separates the rule that applies to your product, what each product documents for lots and manufacturing, the license math at 25, 50, and 75 full users, and the lines a bidder should price outside the subscription. A buyer on a forum put the sizing question as headcount plus manufacturing type: "Small to midsized is pretty subjective. How many people total, and what type of manufacturing are you doing?" Whether you make to order, hold stock, or run batches decides more than the product category on a vendor slide.

Which rule applies to your product

A nutraceutical and a prescription-drug contract manufacturer should not receive the same software answer. The ERP decision starts with which record you must be able to reconstruct, and whether that record will live on paper or in the system.

US drugs, dietary supplements, and Part 11

For a finished drug, 21 CFR 211.188 requires a batch production and control record for each batch. That record includes an accurate reproduction of the master record and documentation that each significant step was done: dates, identity of major equipment and lines, each component batch, weights and measures, in-process and laboratory results, inspection of the packaging and labeling area, actual yield and percent of theoretical yield, labeling specimens, a description of containers and closures, sampling, and the identity of the people who performed and checked each significant step.

Dietary supplement manufacturers follow a different section. 21 CFR 111.255 requires a batch production record every time a batch is manufactured. The record must include complete production and control information and must accurately follow the master manufacturing record. The element list is shorter on the page than 211.188. Your quality unit still has to say what "complete" means for your process.

21 CFR Part 11 applies to records in electronic form that are created, modified, maintained, archived, retrieved, or transmitted under FDA records requirements, and to electronic records submitted to FDA, when the firm uses those electronic records in place of paper. The FDA's 2003 scope guidance, current on the agency page as of 24 August 2018, says the agency intends to interpret Part 11 narrowly. It also says FDA intends to exercise enforcement discretion on the Part 11 requirements for validation, audit trail, record retention, and record copying, while still enforcing predicate rules and controls such as limited access, authority checks, and electronic-signature requirements.

For closed systems, 21 CFR 11.10 still lists validation, the ability to produce accurate copies, record protection, limited access, and secure computer-generated time-stamped audit trails. Those audit trails must not obscure previous entries and must be retained at least as long as the subject records. If the batch record your inspectors read is the signed paper packet, you are in a different design than a plant that releases product from a record that exists only in the ERP. That choice is the cost fork. It decides whether you are buying inventory and production, or inventory, production, and a validated electronic record.

One more US rule sits beside GMP. The Drug Supply Chain Security Act requires an interoperable electronic way to identify and trace certain prescription drugs at the package level as they move through the US supply chain. The FDA page stating that was current as of 16 October 2025. It describes certain prescription drugs. It is a reason to ask quality whether any of your SKUs are in that set. It is not a reason for every nutraceutical brand to buy a serialization suite.

Canadian drugs versus natural health products

Health Canada GUI-0001, the July 2020 drug GMP guide, interprets Part C, Division 2 of the Food and Drug Regulations. It covers fabricators, packagers, labellers, testers, distributors, importers, and wholesalers of pharmaceutical, radiopharmaceutical, biological, and veterinary drugs. It does not cover establishment licensing or active pharmaceutical ingredients. Those have separate guides. GUI-0001 says drug GMP records must allow the complete history of a lot to be traced, and that the quality control department must approve each production batch before sale or supply.

Natural health products follow Part 3 of the Natural Health Products Regulations, not drug GMP in GUI-0001. GUI-0158 version 4 was published on 4 September 2025, is effective 4 March 2026, and replaces the December 2015 NHP GMP guidance. Manufacturers, packagers, labellers, and importers of NHPs need a site licence. Distributors and storage sites must follow GMP, while distributing and storing are not licensable activities. A quality assurance person must approve each batch before it is sold.

Part 11 is an FDA rule. A Canada-only NHP site does not import Part 11 into GUI-0158 by buying US software. A company that also sells a drug or a supplement into the United States still has to map the FDA record for that product. If the US company and the Canadian company are separate legal entities, the multi-entity ERP architecture question is which company owns inventory, which company sells, and which ledger holds the batch release.

What the ERP records and what quality still owns

The ERP is the book of stock, cost, and production activity. Predicate rules and the quality system own batch release, deviations, and corrective and preventive action. Mixing those jobs in one software slogan is how plants buy a second system a year later.

Use the system of record like this:

1. The ERP holds the item, the lot or serial identity, quantities, locations, expiry dates, purchase and sales documents, and the materials consumed and produced on a production order.
2. Quality holds the master manufacturing record, the investigation of a deviation, change control, complaints, and the decision to release or reject a batch.
3. Validation holds the evidence that the configured system, including any custom fields and interfaces, fits the intended GMP use you wrote down.

Odoo quality checks and a Business Central change log can support step 1 and pieces of in-process control. They do not, on the pages cited later, replace the batch record contents in 211.188 or a deviation workflow. A lot history in the ERP, plus the quality process your QA person already runs, covers the plant until an electronic batch record is a stated requirement.

Life-science teams also describe the path off the first accounting tool. "All the start ups start on Quickbooks but move to netsuite in after a year or two." The move is real. The destination does not have to be a large suite if your gap is lots, expiry, and a production journal.

How Business Central and Odoo handle lots, expiry, and batches

Both products document lot identity and expiry in standard inventory. Manufacturing licenses and the shape of the batch record are where the budgets diverge. The ERP for food and beverage lot tracking pattern is the same FEFO idea. Pharma adds the batch record and, for some drugs, package-level tracing.

Business Central item tracking, FEFO, and production

Business Central tracks items by serial, lot, and package number on inbound and outbound documents. Posted tracking sits on item ledger entries. Expiration Date and Warranty Date can be entered when item tracking is enabled, including on item journals. The same page documents a Blocked field on the lot or serial information card that can block a serial or lot number from any transaction. That is a block flag. It is not a documented quarantine-and-release workflow with a quality signature.

Item tracking codes can require an expiration date, calculate expiration dates, and turn on Strict Expiration Posting so the expiration date captured on receipt is respected when the item leaves inventory. Lot-specific tracking forces the outbound transaction to name the lot that entered inventory. FEFO picking applies only when three conditions are true: the item tracking code has warehouse tracking for serial, lot, or package; the item was posted with an expiration date; and the location has Pick According to FEFO turned on. With Strict Expiration Posting, expired items are left out of the pick. If any one of those switches is off, the warehouse will not pick by expiry just because the field exists on the item card. Have the partner show FEFO on your location and your item tracking code before you accept the design.

Production orders carry products, materials, and history of what was manufactured. Consumption and output can be posted manually or flushed forward or backward. The production journal posts component consumption, output, and time. Microsoft documents a workaround for by-products using negative consumption and says Business Central does not have a dedicated by-product feature. A finished production order can be reopened only once. If your batch corrections routinely reopen a closed order, write that limit into the test script.

The change log records direct modifications to the tables and fields the company chooses to track, showing old value, new value, user, and date and time. Microsoft warns that it affects performance and database size, says not to track all fields or ledger entries, notes that entries appear only after the user session restarts, and says retention policies can delete log entries. Treat it as a configurable history of selected fields. Do not treat it as the time-stamped audit trail described in 21 CFR 11.10.

Premium is the plan that includes everything in Essentials plus service management and manufacturing. Essentials is priced as finance, sales, and operations. A plant that issues production orders should budget Premium for the people who run manufacturing. As of October 2026 that list price is USD 110 per user per month in the United States, or CAD 149.20 in Canada, paid yearly. Essentials at USD 80 or CAD 108.50 is the wrong column for a formulation budget.

Odoo 18 lots, four expiry clocks, and quality checks

In Odoo 18, lot tracking is off until Lots & Serial Numbers is enabled. A product is then set to track By Lots. Receipts cannot be validated without a lot number for those products. A traceability report is available from the lot form. That report is the first thing to open in a mock recall: where the lot came from, and which deliveries consumed it.

Expiration dates apply only to goods tracked by lot or serial number. Product settings can store expiration time, best-before time, removal time, and alert time. Those settings compute dates on receipt or manufacture. FEFO must be the location removal strategy, or set on the product category, so deliveries take the soonest expiry. Expiration alerts and a notification to the product's responsible user are documented. Four clocks are useful only if someone owns the alert. Name that user in the design, or the alert lands on a shared inbox and expires in silence.

Quality control points can create quality checks on manufacturing, delivery, and other operations, for selected products or a whole operation. Check types include instructions, picture, register production, pass-fail, measure, worksheet, and spreadsheet. Frequency can be all, random, or periodic. That is an in-process check on a manufacturing or delivery step. On this page it does not become the 211.188 step record. It is not, on this page, the full 211.188 packet with labeling specimens, theoretical yield, and the identity of a second person who checked the step.

The Business Central pages on item tracking, production orders, and the change log, and the Odoo 18 pages on lots, expiration, and quality control points, do not describe electronic signatures equivalent to handwritten signatures under Part 11. They also do not describe a batch record containing the equipment, yield, labeling-specimen, and dual-check elements in 21 CFR 211.188. If those elements stay on paper that the firm relies on, standard lots and FEFO still remove a class of spreadsheet error: shipping a lot that has already expired, or losing the link between a receipt and a delivery. If those elements must be the electronic record, budget a designed batch record and a validation package around it.

Odoo says companies under 50 employees usually implement with Odoo using Success Packs, and companies over 50 employees usually use a partner. Success Packs cover analysis, configuration, training, data import, and, on larger packs, customizations. They are not a published computer-system validation package.

What list price does to a 25, 50, or 75 user budget

"How much does a pharmaceutical ERP cost?" is the search that hides two different bills: the subscription, and the work to configure, migrate, and validate. The tables below are list-price arithmetic on published user prices as of October 2026. They are not a quote. Microsoft states that its prices are informational and may differ at checkout by currency, country, and regional variant. Odoo states that the yearly discount is valid for 12 months for the initial users ordered. Odoo CAD list prices are not taken from the US pricing page here, so Canadian Odoo totals are left for the order form.

Essentials is finance, sales, and operations. Premium adds manufacturing and service management. A company that manufactures should read the Premium column as the full-user license. The Essentials column is there so a finance-only role is not accidentally priced as Premium, and so a manufacturing role is not accidentally priced as Essentials.

• 25 (Essentials, USD per year: 24,000 · Premium, USD per year: 33,000 · Odoo Standard, yearly discount, USD per year: 9,330 · Odoo Custom, yearly discount, USD per year: 18,300)
• 50 (Essentials, USD per year: 48,000 · Premium, USD per year: 66,000 · Odoo Standard, yearly discount, USD per year: 18,660 · Odoo Custom, yearly discount, USD per year: 36,600)
• 75 (Essentials, USD per year: 72,000 · Premium, USD per year: 99,000 · Odoo Standard, yearly discount, USD per year: 27,990 · Odoo Custom, yearly discount, USD per year: 54,900)

Those USD figures are 12 times the monthly list: Essentials USD 80, Premium USD 110, Odoo Standard USD 31.10, Odoo Custom USD 61.00. Standard on the yearly display is Odoo Online with all apps, and hosting, maintenance, and support included. Implementation is not included. Custom adds Odoo.sh or on-premise, Studio, multi-company, and the external API. Odoo.sh hosting is extra. If the yearly discount is not in force, the monthly display prices are USD 38.90 for Standard and USD 76.20 for Custom. At 25 Custom users that monthly display is USD 22,860 per year, which is USD 4,560 more than the discounted USD 18,300.

Canadian Business Central list prices, paid yearly and before tax, as of October 2026:

• 25 (Essentials, CAD per year: 32,550 · Premium, CAD per year: 44,760)
• 50 (Essentials, CAD per year: 65,100 · Premium, CAD per year: 89,520)
• 75 (Essentials, CAD per year: 97,650 · Premium, CAD per year: 134,280)

Essentials is CAD 108.50 per user per month. Premium is CAD 149.20. At 25 full users, Premium is CAD 12,210 per year above Essentials. At 75 full users the gap is CAD 36,630 per year. That gap is the manufacturing plan, not a services estimate.

Shop-floor people should not all be full users. Business Central Team Members are USD 8 or CAD 10.90 per user per month, paid yearly. An Odoo light user is USD 8.90, includes manufacturing shop floor use and inventory barcode operator among other limited rights, and is sold after an advisor quote.

Assume 25 people who need full licenses and 15 people who only post shop-floor or barcode transactions. On US list prices with yearly billing, Business Central Premium plus Team Members is USD 33,000 plus USD 1,440, so USD 34,440 per year. Odoo Custom on the yearly discount for 25 full users is USD 18,300 per year. Price the 15 shop-floor people at USD 8.90 per light user, sold after an advisor quote, and keep that line off the annual total until the order form shows the billing period. The same 25 Premium users in Canada are CAD 44,760, and 15 Team Members add CAD 1,962, so CAD 46,722 per year before tax. If all 40 people were priced as full Premium users, the US total would be USD 52,800 per year (40 times USD 110 times 12), which is USD 18,360 more than the mixed license set. Role design is the discount that does not expire after 12 months.

What Odoo Success Pack hours do and do not cover

Success Packs for a new customer run from Starter through Pro: 4 hours at USD 493, 25 hours at USD 3,060, 50 hours at USD 5,950, 100 hours at USD 10,625, and 200 hours at USD 21,250. Returning-customer prices run from USD 580 to USD 25,000. Travel is extra. Custom modules carry extra monthly maintenance. Odoo says 80 percent of projects in the estimator's manufacturing-included scope go live in 200 hours or less. Those are Odoo consultant hours. They are not a partner implementation scoped to 211.188 batch records, and they are not a validation package. A company over 50 employees is, on Odoo's pricing page, usually on a partner path, so the pack table is a floor for smaller teams and a poor proxy for a 75-user plant.

No public list price in this set is a full project total for migration, configuration, and go-live at 25 to 75 users. Ask each bidder to price data migration, production-order setup, label and lot history, training, and post-go-live support as separate lines. Put computer-system validation on its own line as well, with the records that will be electronic named in the statement of work.

When a specialist system belongs on the short list

Lots, expiry, FEFO, and a production journal are standard work in both products above. Three situations change the short list.

Package-level DSCSA tracing for certain prescription drugs in the US supply chain is the first. General lot tracking identifies a lot. DSCSA, on the FDA page, asks for an interoperable electronic way to identify and trace certain prescription drugs at the package level. If quality confirms that your products sit in that set, ask any Business Central or Odoo proposal to show the serialization and trading-partner exchange, or put a specialist traceability product beside the ERP. If quality confirms your SKUs are dietary supplements or natural health products outside that set, do not buy package serialization to satisfy a rule that names prescription drugs.

An electronic batch record that must carry the 211.188 elements, with signatures that stand in for handwriting, is the second. Standard item tracking and quality checks store lots, quantities, dates, and pass-fail or measured results. They do not, on the cited pages, store labeling specimens, theoretical yield, equipment identity, and a dual check as one controlled batch record, and they do not describe Part 11 electronic signatures. You can keep that packet on paper and let the ERP hold inventory and consumption. You can also commission a designed electronic record and validate it. A specialist pharma ERP is the third path when you want that record as the product's own batch object. Choose it because the record is a requirement, and because you have seen it on your master batch, not because a directory labeled the vendor as vertical.

A single system for deviations, CAPA, and change control is the third. That work belongs to the quality management system. Folding it into the first ERP phase expands the validation boundary to every screen a deviation can touch. Many 20 to 100 person sites keep a dedicated quality system, or a controlled paper and spreadsheet process their QA person already runs, and interface only the release status back to the lot. The Blocked flag in Business Central can stop a lot from moving. It still needs a procedure that says who may set it and who may clear it.

What validation asks you to budget separately

Validation here means documented evidence that the configured system is fit for the intended GMP use. For a closed system, 21 CFR 11.10 names validation among the controls. The 2003 Part 11 scope guidance says FDA intends to exercise enforcement discretion on the Part 11 validation requirement, and that predicate rules remain in force. Discretion on a Part 11 citation is not a reason to skip the evidence your drug or supplement predicate rule expects for the process the software now performs.

Write the intended use in one page before anyone estimates hours. State which records are electronic, who may create and change a lot, whether the change log or another history is in scope, which quality checks are mandatory, and how a released lot differs from a blocked lot in the screens a picker sees. Risk-based effort follows that page. A plant that keeps the 211.188 packet on paper and uses the ERP for quantities, lots, and FEFO has a smaller intended use than a plant whose batch release is an electronic signature inside the ERP.

No Microsoft or Odoo price page in this set states a dollar figure or a week count for computer-system validation or computer software assurance on Business Central or Odoo. Do not let a subscription total stand in for that work, and do not let a Success Pack hour cap stand in for it either. Ask each bidder for a validation line that names the intended use, the documents they will write, the tests they will run on your items, and the hours held for a change after go-live. If they cannot separate that line from configuration, the number is a blended guess.

Interfaces multiply the file. A label printer, a laboratory spreadsheet, and a 3PL each become part of the record path if a batch release depends on them. Include them in the intended use or keep them outside the release decision on purpose.

How to phase a rollout for a 20 to 100 person plant

Phase the system in the order an inspector and a controller both recognize. Our target for a first usable phase is 8 to 12 weeks. That target is ours. It assumes the first phase is finance, inventory, lots, and expiry, with the batch packet still in the quality process you already run. A designed electronic batch record, DSCSA package exchange, or a full deviation module moves the date. "How long does it take to implement a pharmaceutical ERP?" depends on which of those you put in phase one.

A practical sequence:

1. Confirm the rule set: 211.188, 111.255, GUI-0001, GUI-0158, and whether any SKU is a prescription drug under DSCSA. Write the paper-versus-electronic choice next to each record.
2. Clean items, lots on hand, and expiry dates. A traceability report is only as good as the lot captured at receipt. Turn on mandatory lots before you import balances, not after the first cycle count.
3. Configure FEFO and expiry enforcement on the locations that ship. In Business Central that means warehouse tracking, an expiration date on the posted item, Pick According to FEFO, and Strict Expiration Posting if expired stock must stay out of the pick. In Odoo 18 that means lot or serial tracking, the expiry clocks you will honor, and FEFO as the removal strategy.
4. Pilot one product family through purchase receipt, production consumption and output, a quality check, and a shipment. Compare the lot's history to a paper batch you already trust. Reopen rules, by-product workarounds, and who receives expiry alerts show up in that pilot.
5. Add electronic batch content, validation scripts, or a specialist traceability product only after step 4 matches the paper record. Companies that are still forming the quality system can follow the path many young firms describe, off QuickBooks, without jumping to a suite whose transactions the team cannot explain.

License the manufacturing plan for the people who create production orders and release product. Use Team Members or Odoo light users for barcode and shop-floor posting after an advisor confirms the rights. Re-check the Odoo yearly discount at month 12, because the list steps from USD 61 to USD 76.20 for Custom if the discount is no longer applied.

Manufacturing ERP for growing plants is how we phase discovery, configuration, data migration, and training for companies in this size band, including regulated inventory. Platform scope sits on an Odoo rollout or a Business Central rollout. Bring the rule set, a sample batch record, and a user list split into full users and shop-floor users. The first working session should end with a phase-one boundary and a list of lines that are still unpriced, including validation.

How Flectic can help

Flectic connects production, inventory and finance on Dynamics 365 or Odoo for manufacturers of 20 to 100 people, with lot traceability from raw lot to finished serial. Our ERP for manufacturers work also covers real-time WIP, and margin by SKU uses actual cost rolled up per product. Flectic sends a written proposal with a fixed price for each phase before work starts. Book a free discovery call to check whether a Flectic first phase suits your plant.

Sources

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

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

Track items with serial, lot, and package numbers, Microsoft Learn, October 2026.

Set up item tracking with serial, lot, and package numbers, Microsoft Learn, October 2026.

Enable picking by FEFO, Microsoft Learn, October 2026.

About production orders, Microsoft Learn, October 2026.

Auditing changes, Microsoft Learn, October 2026.

Odoo pricing, Odoo, October 2026.

Odoo Success Packs, Odoo, October 2026.

Odoo 18 lot numbers, Odoo, October 2026.

Odoo 18 expiration dates, Odoo, October 2026.

Odoo 18 quality control points, Odoo, October 2026.

Part 11, Electronic Records; Electronic Signatures, Scope and Application, FDA, August 2018.

21 CFR 11.10 Controls for closed systems, Legal Information Institute, October 2026.

21 CFR 211.188 Batch production and control records, Legal Information Institute, October 2026.

21 CFR 111.255 Batch production record, Legal Information Institute, October 2026.

Drug Supply Chain Security Act (DSCSA), FDA, October 2025.

Good manufacturing practices guide for drug products (GUI-0001), Health Canada, July 2020.

Good manufacturing practices guide for natural health products (GUI-0158), Health Canada, March 2026.

Pharmaceutical ERP: The Best Pharma ERP of 2024, ERP Research, 2024.

Best ERP system for small size manufacturing, Reddit, retrieved 2026.

Life science biotech R&D accountants, Reddit, retrieved 2026.