Start small: one product, one destination, one period
You do not need to reorganize an entire catalogue to understand the workflow. Begin with one product, its packaging specification and a small quantity file. This public lesson explains the preparation without a sign-in. The example numbers are fictional arithmetic, not a sample accepted filing or a hidden demo company in your account.
1. Check fit before opening a workspace
Read location guidance, the product FAQ and current plans. A possible exposure signal is not a legal obligation decision. A source page or tutorial also does not prove that a report is available. Ask us about the exact location, period and output you need before paying for a reporting workflow.
2. Gather the source records
- A stable product identifier such as your SKU.
- The packaging specification and when it was used.
- Component material descriptions and empty component masses, with units.
- Supplier evidence supporting those facts.
- Product quantities for the destination and period.
- A list of unknowns and who can resolve them.
Do not upload passwords or unrelated confidential documents. Use the original supplier file where possible rather than a screenshot of a number without context.
3. Products & packaging: identify the item and its components
The workspace area groups Products, Packaging, Materials and Evidence vault. Start from the stable product identity. A finished item can have a container, closure, label and delivery packaging with different sources. Preserve the physical facts separately from any location-specific reporting treatment.
Confirm whether a mass represents one empty component, a filled product, a pack or a case. For this example, a 10 g component used once per item is different from a 10 g package containing several items. Record estimates honestly and follow up with the supplier when a fact is missing.
4. Evidence vault: retain the source
Keep the original supporting document available with the preparation record. Supplier evidence helps colleagues understand a weight or material description; an upload alone does not verify the document or approve a classification. Use the supplier-request workflow when the team needs a specific missing fact. A supplier response link is limited to the requested form, not full workspace access.
5. Imports & sales: review quantities before using totals
This area contains Imports and Sales ledger. Follow the current on-screen template and mapping instructions for the actual import; the prose example here is not a CSV schema. Resolve missing identifiers, destination gaps and case conversions. Keep the source period clear and investigate duplicates instead of assuming that every imported row represents new supply.
For illustration, 1,000 individual units using a 10 g component represent 10,000 g, or 10 kg physically. That arithmetic is easy to check, but it does not settle legal scope, reporting categories, deductions or an accepted program method.
6. Reporting: review gaps and available requirements
The Reporting area includes Data health, Reporting workspaces, Forms & requirements and Reports. Data health identifies source-data issues; zero issues is not a compliance certificate. Location-specific calculations and exports require a complete, independently approved requirements version for the location and period. If one is unavailable, keep preparing source data and ask about coverage rather than improvising an official form.
7. Finish with a reviewable handoff
Another colleague should be able to explain the product identity, component facts, source document, destination quantity, period and unresolved questions. When an output is supported, review it against official instructions before using it. Your organization completes registration, program payments and submission through the required external channel. Keep its acknowledgement after submission; “prepared” and “filed” are different statuses.
Frequently asked questions
Can I read the tutorials without registering?
Yes. The location tutorial library and this walkthrough are public.
Does Canada use a separate form for each province?
No. PackageReports has one Canada-wide packaging workflow. Preserve provincial and territorial destination detail in your source data where a published requirement asks for it. An organization can also use supported U.S. state workflows; plan allowances and reporting coverage are separate.
Does a paid plan guarantee a particular report?
No. Check the exact output and current published requirements first. Send us the location and reporting period if you need clarification.
Can I take my records out later?
Read the company-data export guide for the owner export workflow and what to check in your download.
