01
Enable states
Select program years and show which states are full modules, readiness modules, or tracked-readiness only.
PB
PackBasis Compliance EPR workbench
Command Center preview
Built for Compliance / EHS teams
Unblock EPR reporting
Track state support, registration status, report-readiness blockers, supplier evidence, mapping reviews, assumptions, and compliance package exports from one workspace. Oregon and Colorado fee forecasts stay visible as planning estimates, not the lead workflow.
Static preview
Homepage launch uses non-routed previews only. Future tools can expose readiness blockers, supplier requests, review queues, and compliance package examples before account creation.
The operating problem
Packaging EPR should not run from side spreadsheets.
Compliance owns the reporting clock while source data sits across SKU exports, packaging specs, supplier files, and prior workbooks.
Registration, agreement, and report-preparation status disappear into side spreadsheets when no command center exists.
Supplier evidence, category mappings, and assumptions need review before summaries or forecasts can be trusted.
California and tracked-readiness states need clear boundaries so unsupported outputs are never treated as final.
Compliance-led operating rhythm
From enabled states to an exportable compliance package.
02
Import or assign data
Turn SKU, state-sales, supplier, and packaging files into records with owners, sources, confidence, and review status.
03
Close evidence gaps
Collect missing component data and supplier evidence, then route submitted values back to compliance for approval.
04
Review mappings
Approve Oregon and Colorado category mappings, assumptions, and stale or inferred report inputs before export.
05
Prepare outputs
Generate Oregon and Colorado report summaries first, with fee forecasts clearly marked as planning estimates.
06
Export packages
Package summaries, source records, unresolved issues, evidence, approvals, and assumptions for human review.
Supporting contributors
Every supporting workflow routes back to compliance readiness.
PackBasis does not split the MVP into separate finance, legal, supplier, procurement, or sustainability modules. Contributors complete fields, evidence, reviews, and exports that help the Compliance / EHS owner know what is ready.
Compliance owner
Primary personaOwn the command center.
Track state support, registration status, report-readiness blockers, supplier reviews, mappings, assumptions, and export readiness from one workspace.
Internal contributor
Data inputComplete the missing fields.
Add SKU, sales, packaging, supplier, or evidence data where assigned, with each update tied back to the compliance workflow.
Supplier contributor
Evidence sourceRespond without workspace sprawl.
Submit requested component weights, material details, and supporting files through constrained request workflows.
Reviewer
Human reviewApprove the records that matter.
Review category mappings, assumptions, supplier responses, evidence, and report packages before they are treated as ready.
Read-only viewer
VisibilitySee the package, not a new workflow.
View permitted reports, forecasts, evidence indexes, approvals, and exports without owning compliance tasks.
Readiness tools placeholder
The public scan should preview blockers, not final filings.
These tools are planned but not routed in this homepage pass. They are shown here as the future no-signup surface for readiness blockers, supplier requests, review queues, and compliance package previews.
Readiness diagnostic
A no-signup view of missing SKUs, packaging gaps, evidence coverage, and state-support status.
Placeholder
Action queue draft
A preview of blockers by owner, due date, state, priority, and review status.
Placeholder
Supplier evidence request
Structured packaging data requests for missing material, weight, revision, and support files.
Placeholder
Compliance package preview
A fictional export showing summaries, source records, assumptions, unresolved issues, approvals, and evidence.
Placeholder
U.S. packaging EPR readiness
State-aware, with unsupported actions kept explicit.
Oregon
Full module
Registration status, data readiness, category mapping, material quantity summaries, fee schedules, planning forecasts, exports, and audit packs.
Colorado
Full module
Registration status, data readiness, category mapping, material summaries, fee or dues forecasts, flat-fee or low-volume screening where configured, and traceable exports.
California
Readiness module
Registration readiness, covered-material preparation, source-reduction fields, evidence tracking, and missing-data checklist. Exact fee forecasting is not an MVP output.
MN, MD, WA, ME
Tracked readiness
State presence, source tracking, readiness status, and future-module gaps. No fee forecasts or final report outputs during MVP.
Methodology posture
Source-linked readiness, transparent estimates, and human review.
PackBasis is designed to expose jurisdiction, program year, source configuration, rule status, confidence status, evidence status, mapping status, review status, and unresolved issues so reviewers can see the basis for each output.
Legal boundary
PackBasis provides workflow support, data organization, reporting preparation, readiness assessment, source-linked guidance, and fee forecasts for planning and review. PackBasis does not provide legal advice, does not determine whether a company is legally obligated, does not guarantee regulatory compliance or fee savings, does not directly file into external portals during MVP, and does not replace review by qualified counsel, advisors, official program materials, or the relevant agency, producer responsibility organization, or stewardship organization.
Next conversion placeholder