Shopware 6
Purpose
An existing Shopware 6 installation becomes a sales channel — the item master stays here, the shop gets a copy. This is the route for businesses that want to keep their shop and still carry only one stock figure.
Scope
- Admin API with an OAuth2 client.
- Create and update through the same call:
PATCHwhen the id is known, otherwisePOSTwith a
UUID we assign ourselves. Shopware accepts given ids — which makes creation repeatable instead of „possibly duplicated".
- Prices as a list per currency, sent gross and net: otherwise Shopware recalculates per
customer group and the shelf price no longer matches.
- Stock, orders and fulfilment as with any channel.
- Five settings per channel: installation address, tax, currency and sales-channel ids, plus the
tax rate itself.
Interplay
The channel is a sales channel in the sense of Channels — not a special path beside the document. Items, prices and stock come from the product catalogue and stock; incoming orders become regular sales orders and travel through warehouse, shipping and invoicing like any other order. Credentials live as an integration under Integrations in the encrypted store. Flows and mappings at the system boundary — which field goes where, when a sync runs — belong to OctiConnect; conditions and waiting times remain the business of automations.
Limits
- Shopware needs ids that exist only in THIS installation (tax rate, currency, sales channel).
They therefore live in the channel configuration and are checked before going live; without them every product creation is refused, and the message names only the missing field.
- The real run is still outstanding. What is verified is that we ask correctly and read the
answer correctly — not that Shopware accepts the request. A real seller account is missing.