AstroBaaS

Orders & fulfilment

Energy Label Generator (EU)

Paid pluginsize Mplanned, not built

Indicative price, not an offer: €24/mo; per-country obligation: EU energy-label data + PDF generation

Generated from docs/plan/paid/energy-label-generator/PLAN.md in the AstroBaaS repository. Nothing described below is implemented — it is the written plan for it.

An EU energy label system that generates compliant energy labels for electronics and appliances, validating product data against EU Directive 2017/1369.

The problem

EU: electronics and appliances need energy labels; non-compliance results in fines.

What it does

  • Attach energy label metadata to product (EU energy class A-G, kWh per year, etc.)
  • Generate energy label PDF per EU Directive 2017/1369
  • Display label image on product page and in order
  • Validation: reject products without energy label in EU region
  • Multi-country support (EU only initially)

What it deliberately does NOT do

Each boundary carries its reason. A boundary without a reason gets crossed by the next person who reads this.

  • Energy data import — merchant manually enters; we don’t scrape manufacturer sites. Reason: data accuracy liability.
  • Label translation — labels are in English; merchant translates if needed. Reason: language customization is merchant’s responsibility.

Data model

New tables: EnergyLabel {id, productId, energyClass (‘A’|‘B’|…|‘G’), kwhPerYear, fuelType, model, imageUrl, createdAt}. No migration.

API

  • POST /api/products/:id/energy-label
  • GET /api/products/:id/energy-label
  • GET /api/products/:id/energy-label/pdf

Every route added here must also appear in src/pages/openapi.json.ts — a test fails the build if it does not.

Admin

Product edit page: energy label section (class, kWh, model). Generate and preview label PDF. Bulk import from CSV.

The seam — why this is paid

Core owns: label storage, PDF generation interface. Paid owns: EU compliance validation, per-country rules, fines mitigation.

Per-country obligation: EU energy-label rules, we generate compliant labels

Dependencies

  • Product database

Acceptance checks

Each of these must be able to fail. Before claiming this is done, break the code deliberately and watch each one go red.

  • Product with energyClass=‘A’ generates valid EU energy label PDF
  • Products sold in EU region without label trigger admin warning
  • Label PDF is correct format and contains required fields per Directive 2017/1369

Risks

Non-compliance fines: if label is missing or incorrect, merchant faces EU fines; mitigation: admin warning + validation, but ultimate responsibility is merchant’s.

Commercial context

Suggested price€24/mo; per-country obligation: EU energy-label data + PDF generation
Rival anchorMagento: ~€40 extension; custom: €1500+

The anchor is what the nearest equivalent charges on Shopify or Magento today. It is context for a pricing decision, not the decision.


Generated from the commerce plan. See docs/COMMERCE-PLAN.md for the full catalogue and ../../AI-GUIDE.md for how to work on this repository.