ERP
plentyONE
The e-commerce ERP plentyONE is connected through its standard API. Variations come out as Commerce Bundle products, with the item's texts, the price of a sales price, barcode, category and stock if needed.
In the other direction, orders are created with the prices paid and shipping costs; status and tracking numbers come back.
An order plentyONE already knows by its number is skipped.
- plentyONEERP
- ConFlowIOintegration platformRun active
- Shopware 6
- Shopify
- WooCommerce
- 7ready-made building blocks
- 21data models in the Commerce Bundle, one mapping for every target
Building blocks
Seven building blocks for plentyONE
- Read articlesRead
Reads variations as Commerce Bundle products, in full or only those changed since the last run, with the item's texts, the price of a sales price, barcode, category and stock if needed.
- Read stockRead
Reads stock as lean records, net or physical, in total or per warehouse. A variation without stock keeping is skipped rather than reported as zero.
- Hand over ordersWrite
Creates orders with the prices paid and shipping costs. Known orders are skipped, missing contacts created on request.
- Read ordersRead
Reads orders back with status and tracking numbers, to report the shipment to the shop or marketplace.
- Cancel ordersWrite
Cancels the order when it was cancelled in the shop — as long as it has not been shipped.
- Read master data and documentsRead
Reads, with plentyONE's field names, contacts, companies, addresses, order documents, sales prices, categories, manufacturers, stock levels and master data such as payment methods and shipping profiles.
- Free request
For everything there is no ready-made building block for: a request to the API, with the stored credentials.
In practice
Two workflows with plentyONE
Variations and stock into the shop
plentyONE holds items, variations and stock; the shop should show the same state.
- Triggerschedule
- Readvariations from plentyONE, only those changed since the last run
- Stocknet or physical, in total or per warehouse
- WriteShopware 6, Shopify or WooCommerce
One mapping onto the Commerce Bundle, and the last building block decides which shop is written. A variation without stock keeping does not report a stock of zero.
Orders into the ERP — and back
Orders from the shop and marketplaces should end up as orders in plentyONE without manual work, with the shipment report to follow.
- Triggerthe shop's webhook or a schedule for the marketplaces
- Hand overas an order to plentyONE, missing contacts created on request
- Read backstatus and tracking numbers
- Reportthe shipment to shop and marketplace
No order is re-entered by hand, none is created twice — an order plentyONE already knows is skipped.
Good to know
What to know about plentyONE
- PrerequisitesWhat has to be set up on your side.
- A plentyONE back-end user with access to the API
- The sales price that should go into the shop
- Not coveredWhat ConFlowIO does not write to plentyONE.
- Items and variations are read but not written to plentyONE
- The same goes for stock and prices — they come out of plentyONE, not in
- An order is cancelled only as long as it has not been shipped
- DurabilityApplies to this integration as to every workflow in ConFlowIO.
- Failed steps retry themselves
- Large reads are processed page by page, each page a step of its own
- A failed run is continued rather than started over
- Live logs per step, with credentials removed
Works well with
What works with plentyONE
Frequent partners
Variations and stock out, orders in.
Contact
See plentyONE on your own data
We are glad to show ConFlowIO on your own data. Bring a real slice of your items or orders.
The difference shows at real volumes — not at five sample records.
Would you like to read our whitepaper? Just say so in your enquiry and we will send it to you.
Rather write directly?info@conflowio.com