Roles & permissions
How the Wine2You role model works and which role to build your integration for.
Roles & permissions
Wine2You has one onboarding flow and three roles. A partner is onboarded once and then enables the roles it needs — there is no separate "supplier portal" and "retailer portal".
The role matrix
| Capability | Originator | Fulfiller | Seller |
|---|---|---|---|
| Publish canonical wines | ● | ||
| Create offers (stock + price + permissions) | ● | ||
| Set who may sell / to which countries | ● | ||
| Hold stock at locations | ● | ||
| Fulfil pickup / shipment | ● | ||
| Provide duty & tax context | ● | ||
| Create listings from network offers | ● | ||
| Set shelf price & sales channels | ● |
A partner may enable any combination. A wine estate is typically Originator + Fulfiller; a curated shop is typically Seller only.
Which role should you build?
- Building the supply side (you own the wine)? → Originator guide
- Managing physical stock and fulfilment? → Fulfiller guide
- Curating a shelf with your own prices? → Seller guide
Permissions (Originator-controlled)
An Originator sets, per offer:
network_shareable— whether the offer is visible on the network at allpermissions.allowed_countries— the countries a seller may sell intopermissions.named_sellers— an explicit allow-list of sellerspermissions.default—anyornonefor callers not otherwise named
These are enforced on the read path for every caller — see Data-exposure controls.
Credentials
| Role | Credential |
|---|---|
| Storefront / publishable | publishable key |
| Partner-scoped admin | secret key (server-side only) |
| Machine-to-machine edge access | Cloudflare Access service token |
See the Partner Onboarding reference for the full checklist.
Edit this page on GitHub ↗