What PIE does

One structured catalogue, checked against the rules that actually apply, delivered wherever your buyers are.

Most product-data tools are shaped like a database with a nice front end: they store what you type and hand it back. That is not the hard part of food product data. The hard part is knowing whether what you typed is complete, whether it is legal in the market you are selling into, whether it matches what is printed on the pack, and how to get it — correctly, and in the right shape — to a dozen partners who each want something different.

PIE is organised around those four problems. Everything below is one platform and one record: the compliance engine reads the same product the syndication engine publishes, and the passport a shopper scans is a projection of the same data your buyer sees through the API.

For producers and suppliers

Structured multilingual catalogue: Define the fields your category needs, not the ones a generic tool imagined. Values can be translated per market and per language, with a canonical version underneath, so a French description never silently overwrites the German one.
Compliance validation for the EU: Food information and labelling, organic, deforestation due diligence, hazard analysis, IFS and BRC, health claims, novel food and packaging — evaluated against your actual data, per market, with a clear list of what is missing and why it matters.
Data-quality scoring: Author your own completeness profiles and score every product against them, per language. Use them as a soft signal, or as a gate that blocks publishing until the data is good enough.
GS1 readiness — on every plan: Validate GTINs and GLNs, map your fields to the GS1 Global Data Model, and see a readiness score that tells you exactly how close you are to retail-grade data. Included on the free plan, because knowing where you stand should not cost anything.
Data-pool publishing: When a retailer requires published data, the connector sends it to the data pool — using the record you already maintain, in the shape the standard expects, rather than a fresh spreadsheet.
Digital assets: Product images, specification sheets and certificates in a shared library, linked to as many products as they belong to. Renditions are generated to the sizes your channels ask for.
Syndication and Shopify: Publish to a Shopify store, a marketplace, or a file drop, with a per-channel mapping that reshapes your data to what the destination expects. Publish once; every channel follows.
Approval workflows: Configurable review flows with deadlines, reminders and parallel approvals, so nothing reaches a buyer before the person accountable for it has seen it.
Passports and brand portals: Publish a Digital Product Passport behind a QR code, or a public brand page, snapshotted at publish so what a shopper scans cannot drift from what you approved.
AI assistance, with your own key if you prefer: Extract product data from a supplier PDF or spreadsheet, draft descriptions, and translate — reviewed by a person before anything is saved. Bring your own model key on any plan, including the free one; your key is encrypted at rest and never shared.

For buyers

Catalogues you have been granted: Browse and search current product data from the producers who have granted your organisation access, in the languages you work in. A fresh account is empty until somebody grants you something — nothing leaks by default.
Supplier onboarding: Invite a supplier with a scoped link. They submit data in their own format and language; your field mapping normalises it, and a quality profile you author decides whether it is complete enough to accept.
Quality gates you define: Decide what “good data” means for your business and apply it consistently, instead of discovering the gaps when a product is already in your system.
Integration by API and webhook: Pull the catalogue through a documented REST API, or subscribe to signed webhooks and be told when something changes. Your team manages its own API keys.
Search and filtering: Search across everything you have been granted, with facets for the attributes that matter to your assortment decisions.
Your own organisation, your own rules: Invite colleagues, assign roles, manage API keys, configure single sign-on, and see an audit trail of who did what.

Platform and trust

Isolation enforced at the storage layer: Every organisation's data is separated below the application, so a bug in a query cannot expose another tenant's products. Sharing happens only through explicit grants.
Hosted in the EU: Your data stays in Europe, and you can export all of it — catalogue, assets and history — at any time, on any plan, at no charge.
Single sign-on and MFA on every paid plan: SAML and OIDC single sign-on, multi-factor authentication and session policy are part of the product, not an upgrade.
A complete audit trail: Who changed what, when, and from where — searchable and exportable, on every plan.
Accessibility: The applications are built and tested to WCAG 2.2 AA, with a published conformance statement. Accessibility is a property of the product, not a tier.
A documented, versioned API: Every capability in the product is an API endpoint, with a published reference, stable error codes, predictable pagination and signed webhooks. The apps are clients of the same API you get.