Products & packaging data
Every number Oblifee produces - your EPR fees, recyclability ratings, labelling checks and reports - is calculated from the same small set of facts about what you sell. This section is about getting those facts in and keeping them current. It is written for whoever owns the data: the person filling in the first products, and the admin wiring up a storefront or ERP later.
What Oblifee needs
Oblifee works from four kinds of data. You do not need all of it on day one - you can start with products and add the rest as your obligations come into focus.
| Data | What it is | Why it matters |
|---|---|---|
| Products | What you sell - an SKU, a name, a brand, and optional identity (barcode, dimensions, net weight). | The thing every other fact hangs off. |
| Packaging | The materials, weights and pack structure around each product. | Drives EPR fees, recyclability (RAM) and PPWR readiness. |
| Volumes | How many units you placed on each market, month by month. | Turns per-unit packaging into tonnage, and tonnage into fees and threshold checks. |
| Markets | The nations where you sell. | Selects which rules, fees and labelling requirements apply. Markets are inferred from the volumes you record, so you rarely set them by hand. |
:::info Products come first Packaging and volumes both attach to a product by its SKU. Load your products before (or in the same pass as) their packaging and volumes, or those rows have nothing to attach to. :::
Three ways to get data in
There is no single "right" path - most workspaces use a mix. Enter a handful of products by hand, bulk-load the rest from a spreadsheet, then let a connector keep volumes fresh.
| Path | Best for | Where to go |
|---|---|---|
| By hand | A few products, or filling gaps a sync leaves behind. | Products, Packaging |
| CSV import | Loading many products, packaging rows or volumes at once. | Bulk import |
| Connector or API | Keeping products and volumes current automatically. | Integrations & API |
Whichever path a row takes, it passes the same PII firewall: Oblifee only ever reads the compliance fields it needs - SKUs, materials, weights, quantities, markets and periods. Names, emails, addresses and order references in a file or a feed are dropped at the boundary and never stored. See Bulk import and Security & trust for how that works.
Where to go next
- Products - create and edit a product, and set its identity and brand.
- Packaging - break a product down into components, materials and packs.
- Volumes - record what you placed on each market over time.
- Bulk import - the CSV templates and the AI-assisted mapping flow.
- Integrations & API - connect Shopify, Squarespace or your ERP.