PlentyONE

PlentyONE, until recently branded plentymarkets, is the multichannel commerce ERP from plentysystems in Germany. Agents sync orders out to warehouse, accounting or reporting systems, push stock levels to marketplaces, and maintain the catalog and accounting documents from one back end.

83 actions Session available

PlentyONE website Platform Documentation Capability data verified 2026-08-26

A stocktake count sheet arrives from the warehouse for one PlentyONE installation

Search Variations resolves each counted SKU to its variation, honoring the channel suffix where a SKU carries one

List Warehouse Stock reads physical, reserved and net stock so the agent can compute a variance for every row

The agent separates the rows that agree with the system from the rows that do not

The variance list posts with physical, reserved and net shown side by side for each disputed row

The inventory manager confirms what the counted number means and approves the corrections before Correct Stock overwrites anything

What This Integration Enables

PlentyONE is for merchants who decided their marketplace listings are outputs rather than sources. The eBay account, the Amazon account and the web shop are all downstream of one back end, and the API is shaped by that commitment. Catalog data lives on the item while the number, the price, the stock and the barcode live on the variation. Stock exists per warehouse with physical, reserved and net kept apart. Order statuses are decimals defined per installation rather than a fixed vocabulary. Get those distinctions wrong and a workflow does not fail, it publishes something confidently incorrect to every channel at once.

FlowRunner agents work with the model instead of flattening it. They poll orders by update window and push them into a warehouse, accounting or reporting system. They register shipments with the carrier, generate the invoice and delivery note from the installation's own templates, and email the tracking number out. They book payments, assign them to their orders, and keep the catalog and its per language texts current from a supplier feed. Each of those is a write that reaches customers, carriers or tax records, which is why the human-in-the-loop gate on this connector sits on the numbers rather than on the messages.

Without FlowRunner

Channel numbers drift apart Each marketplace listing is corrected on its own, and every correction is a guess about what the others currently say

Overselling as a rounding error A count from the shelf gets published as available even though some of those units are already reserved against open orders

Repricing by bulk edit A competitor feed turns into a spreadsheet import that touches price types nobody meant to change

With FlowRunner

One number, published outward Stock and price move once in the ERP, and every channel PlentyONE feeds follows from that single write

Reserved units accounted for Stock decisions read physical, reserved and net together, so what reaches a channel is what is actually sellable

Repricing scoped to one price type The flow reads a variation's existing prices first and writes only the amounts that genuinely differ

Use Case Scenarios

The stocktake that does not oversell

A warehouse count lands as a sheet in Google Sheets. The agent reads the rows and calls Search Variations to resolve each counted SKU, which matters because a SKU can be scoped to a single sales channel by a referrer suffix and two channels can carry lookalike codes. It then calls List Warehouse Stock for the warehouse being counted and computes the variance per row against physical stock, keeping reserved and net alongside it. Rows that agree with the system are closed out silently. Rows that disagree post to the inventory channel in Slack with all three figures visible, and nothing is written until a person has confirmed them.
Order to carrier to customer, with the paperwork attached

An order reaches the fulfillment state the installation uses for picked goods. The agent creates the shipping package, calls Register Shipment so PlentyONE requests the label from the shipping service provider, and confirms the booking with Get Shipping Information rather than trusting the response code alone. It calls Generate Order Document for the invoice and the delivery note, downloads them with Download Order Document, and reads the tracking numbers with List Package Numbers. The confirmation goes out through Gmail with the carrier link and the invoice attached. When a shipment has to be withdrawn, the flow calls Cancel Shipment, because deleting the package would leave the carrier side booked and the consignment still live.
Repricing that stops before it makes a product unsellable

A competitor or supplier feed arrives on a schedule. The agent matches each row against Search Variations by SKU, reads the current amounts with List Variation Prices, and calls Update Variation Price only where the amount actually differs, so a run against thousands of rows spends its requests on real changes. Two outcomes leave the automated path. A new amount that falls under the purchase price recorded on the variation goes to a person with both figures shown. So does any row the feed suggests removing entirely, because Delete Variation Price does not make a product free on that channel, it makes the product unsellable there. Taking a line out of sale is a decision with a name on it, and Update Variation with the active flag turned off is usually the operation the merchant actually wanted.

Human-in-Loop Highlight

Correct Stock is an absolute set, not an adjustment. A quantity of 5 makes the stock 5 regardless of what it was, which is exactly what a stocktake result needs and exactly what makes the number dangerous, because the same figure means two different things depending on who counted it. Physical stock includes units already reserved against open orders. Net stock is what is genuinely sellable. A picker writing "5 on the shelf" and a supervisor writing "5 available" have written the same digit about two different quantities, and PlentyONE publishes whichever one the flow posts to every connected channel. So the agent computes the variance and stops. It posts: "Warehouse 2, variation 88134. System holds 7 physical, 3 reserved, 4 net. Your count says 5. Confirm the count basis and approve, or send it back for a recount." A person answers, then Correct Stock runs against a number whose meaning is settled. The agent could have written it either way in a second. What it could not do was know which merchant the count came from.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

83 actions

Connection

Verify Connection Signs in to the configured installation and reports the resolved base URL, the token lifetime and the concurrent session count without returning the token. It is the one operation that fails purely on configuration, so a failure here means the credentials are wrong rather than an access right being missing on some other route.

Orders

Search Orders Searches orders through the PlentyONE order search, which carries the widest filter set including status, referrer, contact, item, package number and shipping status. The general purpose order read.
List Orders By Date Lists orders filtered by a creation, update, payment or booking date range. This is the route incremental synchronization needs, because it is the only order read with paired from and to filters and can answer what changed since the last run.
Get Order Gets a single order with its items, and optionally its addresses, payments, documents and comments in the same call. Loading the relations is the difference between one request and five when building a fulfillment flow.
Create Order Creates an order from order items, address relations and contact or warehouse relations. Used to bring an order in from a sales channel PlentyONE does not connect to natively.
Update Order Updates an order's status, owner, items, properties or relations. Sending an items or properties array replaces the existing collection rather than merging into it, so a flow reads the order first and sends the full array back.
Delete Order Permanently deletes an order. It is almost never what a merchant wants, because the record and its documents go with it. Reserve it for test and duplicate records.
Cancel Order Cancels an order, moving it to a cancellation status and reverting its stock bookings while keeping the record and any invoice already issued. This is the operation a cancellation flow wants.
List Order Items Lists the lines of one order. Line type matters, because shipping costs, coupons and gift wrap are lines too, so a flow that sums quantities filters on type or it counts the postage as a product.
List Order Status History Lists status change entries, optionally narrowed to one order, one status, one back end user or a date range. This is how a flow answers when an order reached shipped and who moved it.
List Contact Orders Lists every order belonging to one contact. The read behind customer service context and lifetime value reporting.
List Order Statuses Lists every order status configured on the installation with its name per language. Status ids are per installation decimals, so a portable flow reads them here and matches on the name.
List Order Referrers Lists the sales channels an order can arrive from, including the web shop, marketplaces and manually created channels. Referrer ids group by channel family, so two accounts on the same marketplace share a whole part.
Book Order In Books an order in, which is how a reorder or purchase order posts its incoming stock into the warehouse. This changes stock levels, so it is not a rehearsal.

Order Documents

List Order Documents Lists the documents attached to one order, optionally narrowed to a single type. Inlining the content makes the response very large, so a flow lists first and fetches one document afterwards.
Generate Order Document Generates an invoice, delivery note, credit note or order confirmation from the installation's own templates. Generating an invoice is an accounting event, because PlentyONE assigns the next number from the running sequence and the document becomes tax relevant.
Download Order Document Fetches one document by id and stores it in FlowRunner file storage, returning a URL a later step or an email can use. PlentyONE returns documents inline as text rather than as a binary stream, which this operation decodes.

Shipping

List Shipping Packages Lists the packages recorded against one order, each with its tracking number, weight and label. The carrier label can be loaded inline so a flow can print or email it without a second call.
Create Shipping Package Creates a shipping package on an order, which is the container a carrier registration later attaches a label and tracking number to. Creating the package does not contact the carrier.
Delete Shipping Package Deletes one shipping package from an order. If the shipment is already registered, cancel it with the carrier first, because deleting locally leaves the consignment booked.
Register Shipment Registers the order's packages with the shipping service provider, which is the call that books the shipment and returns tracking numbers and labels. It creates a real consignment and costs money at the carrier.
Cancel Shipment Cancels a shipment already registered with the carrier, withdrawing the consignment. This is the correct undo for a registration, because it reaches the carrier as well as PlentyONE.
Reset Shipment Resets the shipment on an order so it can be prepared and registered again from scratch. It tells the carrier nothing, so it recovers a bad local state rather than withdrawing a real consignment.
Get Shipping Information Gets the service provider, shipping status, costs and registration timestamps for an order. The shipping status is the reliable signal that a carrier booking actually succeeded.
Update Shipping Status Updates the shipping status held on an order. It records a state rather than performing one, so it is for reflecting a shipment handled outside PlentyONE.
List Shipping Profiles Lists the parcel service presets configured on the installation, each with its carrier, shipping group and the clients and referrers it applies to.
List Package Numbers Lists just the tracking numbers of an order, which is cheaper than the full package read when a flow only needs them for a shipping confirmation.

Returns and Credit Notes

Create Order Return Creates a return order from a parent sales order for the named items and quantities. PlentyONE models a return as a new linked order rather than as a flag on the original, so the id that comes back is a new order id.
List Order Returns Lists the return orders linked to one parent order, optionally bringing the return slip back alongside each one.
Create Credit Note Creates a credit note order from a parent order, which is how a refund is recorded in PlentyONE accounting. A credit note issued against the wrong order is corrected by a reversal rather than by deletion, so validate the quantities first.

Payments

List Payments Lists every payment record in the installation. It carries no filters beyond paging, so the per order read is usually the better question to ask.
Get Payment Gets a single payment with its amount, currency, method, status and transaction type.
Create Payment Books a payment into PlentyONE, which is how an external provider's settlement is recorded. Creating the payment does not attach it to an order on its own.
Update Payment Updates an existing payment. PlentyONE expects the payment id in the body rather than in the path on this route, which this operation handles.
Delete Payment Deletes a payment record. It removes an accounting record and can leave a paid order looking unpaid, so correcting an amount or a status is usually the better move.
List Order Payments Lists every payment assigned to one order, which is how a flow answers whether an order is actually paid and by how much.
List Payment Methods Lists the payment methods available on the installation with the plugin providing each one. Method ids are installation specific, so they do not carry between accounts.
Assign Payments Runs PlentyONE's automatic assignment over the named payment ids, matching each to an order from its transaction data. This is the step that turns a booked payment into a paid order.

Items

Search Items Searches the parent records that variations hang from, with filters for name, manufacturer and update window. Catalog data lives here while the sellable detail lives on the variation.
Get Item Gets a single item by id in the requested language. The response is the item shell, so variations, images and texts are read separately.
Create Item Creates an item together with its main variation. An item without a variation is not sellable, because the number, price, stock and barcode all live on the variation.
Update Item Updates the catalog level fields of an item, such as manufacturer, condition and customs tariff number.
Delete Item Deletes an item and everything hanging from it, including its variations, images, texts and category links. To take a product out of sale without losing its history, deactivate its variations instead.
List Item Images Lists the images attached to an item with the public URL of the full size image and of each generated preview. The read an image export or marketplace feed makes.
Upload Item Image Attaches an image to an item, either by giving PlentyONE a URL to fetch or by sending the file inline. There is no multipart upload here, so a flow can hand it a link produced by an earlier step.
Delete Item Image Deletes one image from an item along with its links to variations and marketplaces. An image still referenced by a live listing will stop resolving.
List Manufacturers Lists the brands configured on the installation. The lookup a product import runs before creating items.
List Item Attributes Lists the attributes such as size and color that multi variant items build their variations from, optionally with each attribute's allowed values.

Variations

Search Variations Searches variations across the catalog by SKU, barcode, variation number, category, supplier, client, market or update window. This is the workhorse catalog read, because the variation carries the number, price, stock and barcode a synchronization flow needs.
List Item Variations Lists every variation belonging to one item, which is how a flow walks all the sizes and colors of a multi variant product.
Get Variation Gets a single variation with its number, model, purchase price, dimensions, order quantity limits and main warehouse.
Create Variation Creates a variation on an existing item, which is what makes a size or color sellable. A new variation is not visible in a shop until it is active, linked to a client and category, and given a sales price.
Update Variation Updates a variation's number, activity, dimensions, warehouse, order quantity limits and related collections. Turning the active flag off is the safe way to take a product out of sale, because the record, its history and its marketplace links survive.
Delete Variation Deletes one variation along with its prices, barcodes, stock records and marketplace links. It is irreversible, and deactivating is almost always the right operation instead.
List Variation Texts Lists the per language texts of a variation, which is where the customer facing name, description, URL path and meta tags live. A shop export that reads only variations comes back with no product names, which is why this read exists.
Update Variation Text Updates the customer facing texts of a variation in one language. The description fields accept markup and PlentyONE stores exactly what it is given.

Prices

List Sales Prices Lists the price definitions of the installation, which are the types such as retail or a channel specific price rather than the amounts. A flow reads a price id here before attaching an amount.
List Variation Prices Lists every sales price attached to one variation with its amount. This is the read a repricing flow makes before deciding whether an update is needed at all.
Set Variation Price Creates the link between a variation and a price type and sets the amount. Used the first time a variation is given that price type, because a repeat is rejected rather than merged.
Update Variation Price Changes the amount of a price already attached to a variation. This is the repricing operation, because it touches one price type on one variation and leaves every other channel price alone.
Delete Variation Price Removes the link between a variation and one price type. Removing the price a channel sells at makes the variation unsellable there rather than free, so a flow checks what the price type feeds first.

Stock

List Warehouses Lists the warehouses configured on the installation with their type and storage location settings. Every stock operation is scoped to a warehouse, so this is the first call a stock flow makes.
List Warehouse Stock Lists the stock rows of one warehouse with physical, reserved and net stock and the reorder level for each variation. Net stock is the sellable number, because physical stock includes units already reserved for open orders.
List Variation Stock Lists one variation's stock in every warehouse it is held in, with physical, reserved and net per warehouse. The read behind the question of how many exist anywhere.
Correct Stock Sets a variation's stock in a warehouse to an absolute quantity against a recorded reason. This is how a stocktake result is posted, and it is the operation this page's human gate exists for.
Book Incoming Stock Adds units to a variation's stock in a warehouse against a purchase price, a supplier and a reason. This is an adjustment rather than an absolute set, which is what a goods receipt needs.
Book Outgoing Stock Removes units from a variation's stock in a warehouse against a reason. It is not tied to an order, so it reduces stock without fulfilling anything in the order system.
Redistribute Stock Moves stock between storage locations or warehouses without changing the total held. Batch and best before managed variations need those values in each entry so PlentyONE can identify the units moving.
List Stock Movements Lists the movement log of a warehouse, recording every booking with its reason, quantity and process. Movements older than three months sit in an archive that a query has to ask for explicitly, and one request cannot span both.

Contacts

List Contacts Searches CRM contacts by email, name, postcode, class, country, referrer, tag or date range. The exact email filter is what a deduplication lookup uses, while the fuzzy one suits a support search.
Get Contact Gets a single contact with its names, email addresses, phone numbers, class, rating, language and referrer.
Create Contact Creates a CRM contact. The vendor's published request schema names far fewer fields than the route actually accepts, so this operation exposes the full contact model.
Update Contact Updates a contact's names, contact details, class, rating, language or blocked state. Supplying tag ids replaces the contact's tags rather than adding to them, which is easy to trigger by accident.
Delete Contact Deletes a CRM contact. It is irreversible and it removes a record that orders reference, so an erasure request is usually better served by the anonymization route that keeps order history intact.
List Contact Addresses Lists the addresses linked to a contact, optionally narrowed to invoice or delivery addresses. PlentyONE stores addresses in generic numbered fields rather than named ones, which a mapping step has to account for.
Create Contact Address Adds an invoice or delivery address to a contact, optionally as the primary one of its type. PlentyONE deduplicates, so the id that comes back may be a record that already existed.
List Contact Classes Lists the customer classes configured on the installation. A class is what gives a group of customers their own prices, payment methods and shipping profiles, so this is the lookup a business to business pricing flow reads.

Stores

List Webstores Lists the clients, which PlentyONE also calls stores, each with its plenty id and store identifier. The plenty id returned here is what every multishop filter refers to, so this is the first lookup a multi store flow makes.

Frequently Asked Questions

What can FlowRunner do with PlentyONE?

FlowRunner agents can run Verify Connection, Search Orders, and List Orders By Date in PlentyONE, plus 80 more actions.

Does connecting PlentyONE to FlowRunner require OAuth?

No. PlentyONE connects to FlowRunner with session-based authentication, no OAuth flow required.

Can PlentyONE trigger a FlowRunner workflow automatically?

PlentyONE doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with PlentyONE

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us