Home › Guides

Add product regulation to an ERP localization project

An ERP can issue the correct local invoice while missing the records needed to trace a food lot, identify a medical device or close an excise movement. Add the product and operator role to the country assessment before choosing the required controls.

This guide scopes three separate EU workflows. It helps you identify the implementation work and specialist owner. It does not declare a product legally marketable or combine food, devices and excise into one certification checklist.

Use the regulated-product discovery worksheet to record the relevant population and evidence. The controls and worked quantities below are proposed operating tests.

Define the product and the operator's role

Record the product classification, intended use, market, legal manufacturer or supplier, and the activities your entity performs. Manufacturing, importing, distribution, storage and transport can trigger different requirements even for the same item.

Give the specialist the real activity and product evidence. A stock description such as accessory or sample is insufficient when classification affects the applicable regime. Preserve the approved classification and its effective date separately from a sales category used for management reporting.

Assign regulatory affairs or the relevant product specialist to legal scope. Quality owns release and recall decisions. Warehouse operations owns physical identity and movements. Tax or excise specialists own duty treatment. Finance owns valuation and reconciliation, while the application owner implements the approved data flows.

Design a food-lot traceability test

The Commission explains food traceability and the need to identify suppliers and business recipients, with additional rules for specific sectors. Establish the applicable sector requirements before defining records for animal-origin foods, sprouts or other specialized categories. European Commission, food-law general requirements.

For an ordinary distribution exercise, link supplier receipt, product, lot, quantity, storage location and business-customer shipments. If repacking or processing changes lot relationships, preserve the transformation. Do not retain only the supplier's lot in a free-text note that disappears when the warehouse relabels the stock.

Consider a synthetic 1,000 kg lot. The warehouse ships 300 kg to business customer A and 400 kg to business customer B. It retains 200 kg and records 100 kg as documented waste. The quantity bridge is 300 plus 400 plus 200 plus 100, or 1,000 kg.

During a recall exercise, quality must locate the 200 kg on hand and identify the 700 kg distributed to those two recipients. It must also retrieve the waste evidence. The 100 kg is not assumed available for recall, but its disposition still explains the original population.

If the ERP shows only 900 kg of accounted movements, open a 100 kg traceability exception. Do not make an unsupported stock adjustment solely to balance the exercise. Investigate warehouse records and identify whether stock, shipment or waste information is missing.

Define device identifiers and registration ownership

For medical devices, preserve the regulatory identity required for the actual product and role alongside the internal SKU. The Commission's UDI explanation describes the device identification and traceability framework and conditional record responsibilities. A generic barcode field is not proof that all required identifiers and relationships are captured. European Commission, unique device identifier.

Have regulatory affairs determine the required identifier level, actor responsibilities and applicable transitional treatment. Record who maintains the authoritative device data and how packaging, batch or serial information connects to stock movements where required. Keep supplier data changes subject to approval.

As of 28 May 2026, the Commission lists four EUDAMED modules as mandatory: actor registration, UDI/device registration, notified bodies and certificates, and market surveillance. Their users and duties differ. This does not mean every distributor must perform every module's functions. European Commission, EUDAMED overview.

In a synthetic test, receive 50 devices with approved identifiers, ship 30 and retain 20. Select one affected batch or serial population and retrieve its supplier and shipment evidence. If the interface replaces regulatory identity with an internal SKU, stop release of that mapping. Preserve the identifiers and have the specialist approve their restored relationship before relying on the report.

Keep excise authorization and movement closure distinct

The Commission describes EMCS documents for relevant duty-suspension and duty-paid movements and the report-of-receipt process. Operator authorizations and goods categories are checked through the excise-data framework. European Commission, EMCS.

Before dispatch, have the excise owner confirm the actual movement regime, authorizations, goods classification, quantity basis and required document. Store the movement reference against the shipment and invoice. A commercial delivery note cannot substitute for an uncompleted regulatory movement process.

Consider a synthetic covered movement of 1,000 litres under the approved regime. The consignee records 988 litres received and a 12-litre shortage. Retain the actual receipt and discrepancy, then follow the applicable reporting and duty-resolution process. Do not report a fictitious full receipt because the carrier marked the truck delivered.

The physical shortage can affect stock, claims and duty decisions differently. Tax determines the duty consequence and finance determines the accounting treatment. An automatic credit note for 12 litres is not justified solely by the existence of the movement exception.

Connect systems through authoritative references

Decide which system owns product classification, lot or serial history, quality decisions, regulatory submissions and financial postings. The ERP may receive an approved status and reference from specialist software rather than perform the entire regulated process itself.

Preserve the authority or specialist-system result with its subject and timestamp. Keep stock release, invoice issue, regulatory acceptance and movement closure as distinct decisions. Test the handoff from an external system back into the ERP, including failed and delayed updates.

If integration fails after regulatory acceptance, query the existing case before submitting a duplicate. If quality blocks stock after a recall decision, verify that sales allocation and picking also respect the block. A warning in one application is insufficient if another channel can still dispatch the goods.

Approve each scoped workflow separately

Run the food, device or excise test that matches the actual business. Record excluded populations and the reason they require a separate specialist review.

☐ Product, market and operator role have an approved classification.
☐ Required identifiers and document types have authoritative sources.
☐ Stock movements preserve the necessary lot, serial or movement links.
☐ Release, reporting, receipt and closure decisions have named owners.
☐ Recall, missing-identity and shortage scenarios produce explicit exceptions.
☐ Regulatory and financial quantities reconcile without invented adjustments.
☐ Specialist approval identifies the exact accepted product and activity scope.

Use the existing obligation-mapping guide for ownership and master-data guide for approved identifiers. Add the sector tests to localization acceptance.

Sources checked 17 October 2026. National implementation, product-specific detail, authorizations and transitional device rules remain decisions for the actual specialist review.

Worksheet: Regulated-product scope and evidence record

Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment.

Show the worksheet

Use with the regulated-products guide. Complete separate branches for each actual sector, product and operator role. An invoice localization is not evidence of product approval.

Approve scope

Product, market, classification evidence and effective dates: ____
Legal operator and activities: manufacture, import, distribute, store or transport: ____
Applicable specialist, authority and sources: ____
Required identifiers, authorizations and document types: ____
Systems of record and interface responsibilities: ____
Exclusions and separate assessments required: ____

Food traceability branch

Supplier, receipt, lot and quantity: ____
Transformations, relabeling and location relationships: ____
Business recipients and shipment quantities: ____
On-hand, waste and other disposition evidence: ____
Recall decision, stock block and communication owner: ____

Synthetic quantity check: 300 kg to A + 400 kg to B + 200 kg held + 100 kg waste = 1,000 kg. Distributed recall population is 700 kg and the remaining 200 kg is located and held in the exercise.

Medical-device branch

Role-specific registration and transitional decisions: ____
Approved device/regulatory identifiers and SKU relationship: ____
Required batch/serial relationships and authoritative data owner: ____
Receipt-to-dispatch traceability and identifier-error recovery: ____

Synthetic stock check: 50 received - 30 shipped = 20 on hand. This does not itself prove regulatory compliance.

Excise branch

Movement regime, authorizations and goods classification: ____
Shipment and regulatory movement references: ____
Document acceptance, dispatch, receipt and closure evidence: ____
Shortage and duty/accounting decisions: ____

Synthetic receipt check: 1,000 litres dispatched - 988 received = 12 litres shortage. Preserve the actual result and specialist resolution.

☐ Required identities survive system handoffs.
☐ Quality, regulatory and finance decisions remain distinct.
☐ Missing references and shortages cannot be hidden by invented adjustments.
☐ Accepted scope identifies the exact products, roles and activities.

Specialist approval and date: ____

Operations/finance acceptance and date: ____

Country pages: key facts with sources
E-invoicing matrix: country × ERP support
All guides

Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17.

Related: Glossary – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).

Page last updated: 2026-10-17 · Markdown version