About this plugin
Ombel records the packaging used for new WooCommerce orders. Create
packaging profiles with component weights, assign them to products and
variations, include shipping packaging, and review your local records.
The bundled local features remain free, with no expiry or account requirement:
- Packaging profiles, component weights and version history.
- Product and variation assignment, bulk assignment and CSV import/export.
- Order packaging snapshots, local ledger and material totals.
- Missing-data review, registration records and an audit log.
- Local preparation views for manual review and export of your own CSV data.
- Diagnostics that exclude credentials, customer details and raw payloads.
Local recording works without a cloud service and does not block checkout.
Historical orders are not automatically backfilled. A monetary refund does
not automatically deduct packaging mass. Multisite is outside this release’s
scope.
This is a packaging records and preparation tool. It does not certify legal
compliance, determine your obligations, verify official registrations, create
official filing exports or submit declarations. Country guidance and rule
content require your own review. Store records may exclude other sales
channels or producer-wide quantities. Keep your registration and filing process.
Spain adds factual business and packaging details, preserved order snapshots,
and an internal annual view with explicit missing facts. Poland adds annual
recorded material totals and your own administrative CSV for manual review.
Neither view decides producer responsibility or validates complete business
coverage. No official Spanish RPP/Ecoembes or Polish BDO output or submission
is available. Recorded offsets are not validated as Polish reporting deductions.
Austria adds optional packaging component facts, preserved with new order
records, and an internal annual view of recorded material totals and missing
facts. Italy adds an internal annual view of recorded material totals for
manual review. These views do not determine producer responsibility, calculate
scheme fees, verify complete business coverage or provide official reports.
No official Austrian scheme or Italian CONAI export or submission is available.
Denmark adds recorded year and quarter totals, unverified business facts,
component facts preserved for new orders, and saved preparation JSON with
gross weights by declared household or commercial use. Older unknown facts
remain unknown. No producer-role, eligibility or DPA/VANA filing decision,
official upload or automatic submission is available.
Sweden adds recorded annual material totals and separate administrative
periods before and from 12 August 2026, with your own material CSV. Stored
UTC-based dates and recorded offsets do not establish Swedish legal reporting
dates or deductions. Registration, representation, provider categories and
official declarations require separate review.
Guided example
Try this with sample products and a controlled test order on a test shop:
- Open a product’s Shipping tab. In “Create and assign product packaging
here”, name a sales profile “Bottle v1” and add two components: 24 g
paper/cardboard and 1 g plastic. The total is 25 g. Save other product
edits first, then create, activate and assign the packaging in one action.
- Reuse this active profile on 12 products: open Packaging > Bulk assignment,
select their category and “Bottle v1”, preview, review the selected scope
and apply. The same profile can be reused without entering its weights again.
- For SKU imports, export the assignment CSV and keep its column names. Add
each product’s SKU and the exact profile_uuid from the profile export.
Upload once, review “Would assign”, “Would skip” and errors, then apply
the saved preview. The final result shows what was actually changed.
- Set a default shipping profile with 180 g paper/cardboard and 7 g plastic:
187 g for the parcel. Before the order is recorded, its order panel can
keep this default, select another active shipping profile, or explicitly
omit shipping packaging when that matches the physical parcel.
- Complete a qualifying test order containing two units using “Bottle v1”.
Run the background queue and check the order panel: 50 g product packaging
plus 187 g shipping gives 237 g. Material totals are 228 g paper/cardboard
and 9 g plastic. With no packaging corrections, gross and net are equal.
- Open Reports to download your administrative material CSV for the chosen
period, country and material. Review missing-data counts as well as g/kg
totals. This is your own-records CSV for review, not an official filing.
- Clone the profile to a new version when packaging changes. After activation,
review its migration preview before moving future assignments. The order
already recorded retains its 237 g and the original version. Older profiles
without a recorded version relationship use ordinary reviewed bulk assignment.
An incomplete historical order remains marked incomplete after repairing its
current product. A failed recording can be retried from its order panel only
when the original frozen recording context is available. This does not
automatically backfill old orders or change their historical figures.
External services and privacy
This version runs locally without an external service, account or subscription.
Packaging data stays on your WordPress site. No cloud connection or paid
checkout is offered in this version.
The plugin stores packaging materials and weights, destination countries,
local order identifiers and pseudonymous order references. It does not copy
customer names, email addresses, phone numbers, postal addresses or payment
details into its packaging records. Avoid personal information in profile
names and business notes. References are pseudonymous, not anonymous: your
store can associate them with its WooCommerce orders.
No automatic retention expiry or personal-data exporter/eraser is implemented.
Review the retention and erasure requirements that apply to your store.
Deactivation and normal plugin deletion preserve packaging records. Intentional
full deletion requires BRIGHTFERN_PPWR_ALLOW_DATA_WIPE developer configuration;
back up your data before using it.