Skip to content
P

Producer quickstart

Sign up as a producer (PIP), invite your team, create your first product, and publish it to a buyer.

This tutorial walks a Product Information Producer (PIP) — a cooperative, farm, or processor — from an empty account to a published product a buyer can consume. It takes about 20 minutes and mirrors the validated end-to-end path the platform is tested against.

Before you start

You need an invitation token for your producer organisation. Tokens come from a PIE platform admin (or from your own admin console if you already run one). A token encodes the organisation, the plan tier, and the role you will be granted.

1. Register and land in the app

Open the producer app at /register/<token>. The preview screen shows the organisation name and the role the token grants — confirm they are correct, set a password, and submit. On success you land authenticated straight in the dashboard; you are not bounced back to a login screen.

If registration ever falls back to /login?registered=1, your session could not be established automatically — just sign in with the password you just set.

2. Confirm your organisation settings

Open Settings and verify three things:

  • Organisation name matches your business.
  • Plan tier matches what you signed up for (this governs rate limits and feature entitlements — see Plans & limits).
  • Enabled locales cover the markets you sell into. Locales drive per-market compliance and publishing — a product sold in Germany needs de-DE, one sold in Switzerland needs de-CH, fr-CH, and it-CH.

3. Invite your team

Go to Team → Invite and invite a colleague as a pip_editor. Copy the generated token and have them open /register/<token> in their own browser. Editors can create, edit, and publish products and assets but cannot manage users, grants, or API keys — those stay with pip_admin. See Roles & permissions for the full matrix.

4. Create your first product

You can create products two ways:

  • AI ingestion — open Ingestion → New, upload a product spec sheet (PDF or XLSX) or paste a URL. The pipeline preprocesses the document, extracts structured JSON, and stops at a mandatory review step. Correct any field, then approve to create the product. Review is never skippable — the extracted data is always editable before import.
  • Manually — fill in name, SKU, GTIN, and category attributes. Attach an image through the presigned-upload flow (the binary goes directly to object storage, never through the API server), and a thumbnail rendition appears once processing finishes.

For richer downstream data, link a few reference entities — an allergen, a nutrient, a certification — from the seeded system types. GS1, compliance, and DPP steps all read from these.

See the Products guide for versioning, localization, and assets in depth, and the AI guide for ingestion and enrichment.

5. Get to GS1-ready

Create the product in the seeded "Food (built-in)" category and fill the nine required fields (brand, net content, ingredients, allergens, energy, fat, carbohydrate, protein, origin country) plus a valid GTIN and a GPC brick. On a fresh producer org the category ships with nine default GDM mappings, so GS1 readiness reaches "Ready" without hand-mapping a single field — the remaining identifiers are projected from your product columns.

Assign target markets (for example DE and CH). The required locales follow automatically. See the GS1 & GDSN guide.

6. Publish

If your organisation uses the seeded Product approval workflow, submit the product for review as an editor and approve it as an admin — the publish gate blocks publishing until the product is approved. Quality and compliance gates (where enabled) also fail closed: a mandatory rule failing in any required locale blocks the publish until you fix it.

Once the gates pass, publish. You can then publish a Digital Product Passport and view it on its public page. See the Workflow guide, Quality & compliance guide, and DPP guide.

7. Grant a buyer access

Products are private until you grant access. From Grants, expose specific products to a specific buyer (PIC) organisation, optionally with an expiry. The buyer sees only what you grant — isolation is enforced at the database, not in the UI. See the Onboarding guide for the buyer-driven intake flow, and the Buyer quickstart for the other side.

Next steps