====== Store and parts ======

The *//store//// lets programmes sell or reserve ////parts//// tied to team stock. Surfaces include the ////public shop//// and the ////admin catalogue / requests//* tools.

===== Public store (buyers) =====

1. Browse categories and products on ''/en/store'' (locale as needed).
2. Add lines to the basket and proceed to *//checkout//*.
3. Complete contact and delivery details as prompted.

Availability and pricing reflect what your team published in the catalogue.

===== Parts catalog (team admin) =====

*//Parts catalog//* maintains SKUs your team sells:

- Descriptions, images, and pricing
- Stock indicators where used
- Category placement for the public shop

Only teams with the store module enabled see this menu.

===== Store requests (reservations) =====

*//Store requests//// (or ////Price requests//// on the team dashboard) lists incoming ////reservations//* from the public site or internal orders:

- Mark items *//sold//// or ////released//* so stock stays accurate
- Follow up with the customer outside the portal when payment or shipping is manual

===== QR and workshop use =====

Some programmes print *//QR labels//// for bins and parts. Scanning ties consumption to a ////car project//* so disputes on “who used this gearbox” are easier to settle. Ask your super-admin if your team has label printing enabled.

===== Super-admin =====

Super-admins can manage catalogue scope across teams and handle programme-wide store configuration. Day-to-day fulfilment still sits with each team’s store operator.