Product attributes and custom fields

Free — GPL coresize Lplanned, not built

Generated from docs/plan/core/product-attributes-and-custom-fields/PLAN.md in the AstroBaaS repository. Nothing described below is implemented — it is the written plan for it.

This is the same as flexible-product-attributes (slug already assigned). This is likely a duplicate in the input list; the feature has already been planned. Refer to flexible-product-attributes for full plan.

The problem

See flexible-product-attributes.

What it does

• See flexible-product-attributes

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.

• See flexible-product-attributes

Data model

See flexible-product-attributes

API

• See flexible-product-attributes

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

Admin

See flexible-product-attributes

The seam — why this is core

See flexible-product-attributes

Extensibility without code deployment is a base requirement. Compliance fields (GPSR) depend on this.

Dependencies

• See flexible-product-attributes

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.

• See flexible-product-attributes

Risks

See flexible-product-attributes

Commercial context

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.