An online product listing can be removed in minutes, but the records needed to explain that listing may have to remain available for years. If you sell consumer goods into the European Union, product safety is no longer just a manufacturer’s paperwork problem. Your listing, supplier file, customer messages, inventory records, and refund process can all become part of the evidence that you handled a product responsibly.
The General Product Safety Regulation (GPSR) has applied since 13 December 2024. It creates a general safety framework for products sold online and offline, including rules for traceability, distance-sale listings, complaints, accidents, corrective actions, and recalls. The European Commission reported 4,671 Safety Gate alerts in 2025—the highest number recorded and a 13% increase from 2024—along with 5,794 follow-up actions.
This guide translates the regulation into a working system for a small online seller. It is not a substitute for legal advice or product-specific conformity requirements. Use it to identify the records, owners, and controls you should discuss with your compliance adviser.
First, identify your role in the supply chain
The same business can have more than one role. A private-label shop may be a manufacturer because it sells a product under its own name or trademark. A business importing goods from outside the EU may be an importer. A shop that buys finished goods from an EU wholesaler and resells them is generally a distributor. A fulfilment provider may also have specific responsibilities when it handles products for an operator that has no manufacturer, importer, authorised representative, or other responsible operator established in the EU.
Your role determines which checks you must perform and which records you must retain. Do not assume that using a marketplace transfers your obligations to the marketplace. A platform may have its own duties, but the trader who offers the product still needs to know what it is selling and whether the offer contains the required information.
The GPSR broadly covers consumer products placed or made available on the EU market, including products sold for payment or supplied for free. It can apply to new, used, repaired, or reconditioned products. Products governed by more specific EU safety laws are not simply outside the framework; the GPSR can still cover risks and aspects that the more specific rules do not address.
Create a one-page product-role register with these fields:
- product or SKU;
- brand and manufacturer;
- your role for that product;
- country where the manufacturer is established;
- EU responsible economic operator and contact details;
- applicable product-specific legislation or standards;
- sales channels and EU countries served; and
- owner for safety, complaints, and recall decisions.
This register is more useful than a generic statement that your business is “GPSR compliant.” It makes the next decision—what evidence belongs to each product—much easier.
Build a product safety file before the listing goes live
The central obligation is simple: only safe products may be placed or made available on the EU market. The difficult part is showing how you reached that conclusion.
For a product you manufacture or private-label, begin with an internal risk analysis and technical documentation. The file should describe the product and its safety-relevant characteristics, identify reasonably foreseeable risks, and explain the measures used to eliminate or reduce them. Keep test reports, instructions, warnings, packaging artwork, component information, applicable standards, supplier declarations, and approved product versions together.
For a product you distribute, collect enough evidence to perform your checks rather than relying on a supplier’s general assurance. Ask for the manufacturer’s identity, model or batch information, instructions, warnings, and evidence of the relevant conformity work. Confirm that the packaging and product markings match the inventory you actually receive. If the supplier cannot identify the item precisely, you will not be able to identify it precisely for a customer or authority later.
A useful file structure is:
SKU-1042/
identity-and-versions/
supplier-and-responsible-person/
risk-assessment/
tests-and-standards/
labels-warnings-instructions/
complaints-and-incidents/
corrective-actions-and-recalls/Give each document a version and approval date. A product photo alone is not a reliable identifier: retain model numbers, batch or lot codes, barcodes, component versions, and the date range in which each version was sold.
Make the online offer complete, not merely attractive
For distance sales, the product offer must clearly and visibly show key safety and traceability information before the customer buys. At minimum, plan to display:
- the manufacturer’s name, registered trade name, or trademark;
- the manufacturer’s postal and electronic contact address;
- when the manufacturer is outside the EU, the EU responsible person’s name and postal and electronic address;
- information that identifies the product, including a picture, type, and other product identifier; and
- required warnings and safety information in a language consumers in the relevant Member State can easily understand.
Do not hide this information in a general terms page, an image that cannot be read on a phone, or a link that disappears when a marketplace changes its template. It should remain attached to the specific offer and version of the product.
Add a listing-release check to your publishing workflow. The person approving a new SKU should confirm that the listing data matches the product file, the responsible-person information is current, warnings are in the required language, and the offer identifies the exact model or variant. When a supplier changes packaging, components, instructions, or the responsible operator, route the listing back through that check.
This is also a good place to maintain an audit trail. Save the approved listing content and a timestamped snapshot when a product first goes live and when a material change is published. If a marketplace supplies the listing page, export the relevant information instead of assuming the platform will preserve historical versions for you.
Make traceability a normal transaction field
Traceability is not a once-a-year spreadsheet exercise. It is the connection between an item, its source, its destination, and the customer transaction.
For every product movement, capture as much of the following as your role requires:
- supplier, manufacturer, importer, or other upstream operator;
- purchase order, goods-received date, and batch or lot;
- SKU, model, serial number, or other product identifier;
- warehouse location and quantity received;
- sales channel, order number, destination country, and shipment date;
- customer contact information held for safety communications; and
- return, refund, replacement, repair, or disposal outcome.
The GPSR requires economic operators to be able to provide product information for 10 years after they were supplied with the product or supplied it onward. Supply-chain traceability information must be available for six years. Those periods are not a reason to keep every operational document forever, but they are a reason to set retention rules deliberately and test that archived records can actually be retrieved.
If you sell mixed inventory, do not let the SKU become the only identifier. A single SKU can cover several manufacturing batches or packaging revisions. Use lot, serial, or version fields where a safety notice could apply to only part of the stock.
Turn complaints into a safety signal
Customer support often sees the first evidence that a product is unsafe. A complaint such as “the charger became hot,” “the clasp broke,” or “the child swallowed a small part” should not disappear into a general inbox.
Create a product-safety complaint register with at least:
- date received and communication channel;
- product, model, batch, and order identifier;
- customer’s description of what happened;
- injury, property damage, or near-miss information;
- photos, videos, returned-item details, and other evidence;
- initial risk classification and escalation owner;
- supplier or manufacturer notification date;
- investigation findings and corrective action; and
- link to any refund, replacement, recall, or authority notification.
Separate ordinary dissatisfaction from a potential safety complaint, but do not make the threshold so high that staff ignore early signals. A cluster of small failures can matter even when no customer reports an injury. Review the register on a fixed schedule and trigger an immediate escalation for an alleged injury, fire, electric shock, choking hazard, chemical exposure, or other serious risk.
When an accident caused by a product comes to your attention, use the applicable Safety Business Gateway process without undue delay and coordinate with the manufacturer and responsible person. The correct reporting party can depend on the product and role, so document who made the decision and why.
Prepare the recall workflow before you need it
A recall is an operational event, not just a notice on a website. You need to stop further sales, identify affected units, contact customers, coordinate with upstream operators, and account for the financial consequences.
Write a short recall playbook with named owners for:
1. Containment
Pause listings, paid ads, replenishment, and fulfilment for the affected product and any related batches. Quarantine physical stock and mark the system so a replacement shipment cannot accidentally release it. Tell every sales channel what identifier and date range to block.
2. Scope
Use the lot, serial, version, and order records to identify affected units. Reconcile the number sold, in stock, returned, destroyed, transferred, and still unaccounted for. If you cannot determine the scope, record the conservative assumption and get specialist advice.
3. Notice and direct contact
Use clear language describing the product, the hazard, the affected identifiers, what the customer should do, and how to obtain help. When a recall notice is provided in writing, use the required recall-notice format. Contact affected customers directly using the customer data available to you, not only a general homepage banner.
4. Remedy
Plan the logistics and accounting for repair, replacement, or an adequate refund. A customer should not have to pay to return a dangerous product or wait indefinitely for a remedy. Keep evidence of the offer, the customer’s choice, shipment or refund date, and any failed contact attempt.
5. Closure
Report progress, update the product file, retain the final population reconciliation, and document when the listing and stock controls were released. A recall is not complete merely because the product was removed from one storefront.
Keep the financial records aligned with the safety records
Product safety work changes the numbers in your books. A withdrawal can create scrapped inventory, a recall can create refund and shipping costs, and a replacement program can create new fulfilment transactions. If the operational and accounting records use different identifiers, the financial impact will be difficult to prove.
Track recall-related activity in separate accounts or dimensions, such as:
- inventory write-down or disposal;
- customer refunds;
- replacement product cost;
- return shipping and reverse logistics;
- testing, inspection, and consultant fees; and
- supplier recoveries or insurance proceeds.
Reconcile the safety population to the ledger: units affected, units refunded, units replaced, units returned, and units destroyed should each have an explainable balance. Preserve the original sale and then record the refund or replacement with a reference to the recall case; do not overwrite history to make the final totals look tidy.
This discipline also helps with cash planning. A recall can produce an immediate cash outflow even when the original sales were profitable. A monthly product-risk review that includes inventory value, customer exposure, and potential remediation cost gives you a more realistic view of operating cash than a sales report alone.
A 30-day implementation checklist
If your process is still informal, use this sequence:
Days 1–5: inventory the exposure. List every consumer product offered to EU customers, the selling channels, the countries served, and the role your business plays for each item. Flag products with batteries, heat, children’s use, ingestion, moving parts, chemicals, or software-controlled functions for closer review.
Days 6–12: close the evidence gaps. Request missing manufacturer, importer, responsible-person, model, batch, warning, instruction, test, and risk-assessment records. Put products on hold when you cannot identify the operator or the product accurately.
Days 13–18: fix the listing and transaction data. Add required fields to your product information management system, marketplace template, order export, and warehouse receipt. Test one listing from every channel on a mobile device and verify that a historical record can be retrieved.
Days 19–24: rehearse a complaint and recall. Use a fictional batch to test escalation, customer matching, channel takedown, quarantine, refund approval, and authority-notification ownership. Measure how long it takes to identify affected customers and reconcile units.
Days 25–30: connect operations to finance. Add recall dimensions to your ledger, establish retention and access rules, assign a monthly reviewer, and produce a sample reconciliation from product population to refunds, replacements, and inventory movements.
The goal is not a binder that looks complete. It is a repeatable chain from product design or sourcing to listing, sale, complaint, corrective action, and final accounting entry.
Simplify Your Financial Management
When product-safety controls create inventory, refund, and recall transactions, transparent records make the work easier to review. Beancount.io offers plain-text accounting that is transparent, version-controlled, and AI-ready; explore the documentation or Fava dashboards to connect financial history with the operational records your team already maintains.
