WiziShop

WiziShop is a French hosted ecommerce platform, with Dropizi as its dropshipping edition. Agents push orders into a warehouse, ERP or 3PL and write tracking back, keep SKU stock in step with a supplier feed, manage products, customers and reviews, and react to store webhooks in real time.

3 triggers 75 actions Session available

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

On Order Event fires when an order is created on the shop

Get Order returns the lines, the addresses and the shipment records the order was split into

Download Picking Slip fetches the document the warehouse actually works from

The label is bought and Ship Order writes a tracking number against each shipment

Set Order Status moves the order along the ladder the customer sees on their account

On SKU Event reports the stock drop the sale caused, compared against the reorder point

A buyer decides what happens to a SKU the sale has taken to zero

What This Integration Enables

WiziShop is a French hosted ecommerce platform, and Dropizi is its dropshipping edition on the same API. This connector covers the merchant facing half: orders and their whole status lifecycle, invoices and slips as real files, products and SKU stock, categories, brands, storefront filters, customers, newsletter and SMS opt in, reviews, storefront scripts, and the webhook surface behind three triggers. Two details change how flows are built against it. Order documents are fetched rather than linked, because the URLs on an order point back at the authenticated API and no browser or downstream service can open them. And the platform publishes one route per order status rather than a status field, which this connector puts behind a single picker so a flow does not need eleven near identical blocks.

Stock is the other thing worth knowing. Update SKU Stock will set an absolute number, and it will also raise or lower one, with the arithmetic done by WiziShop rather than by the flow. That makes a supplier feed and a marketplace feed safe to run at the same time. The connector states the platform's own maturity labels where they exist rather than hiding them, so a flow author can see that Create Order and Create Customer are labeled Alpha before wiring either into a migration. Where a write reaches a customer or destroys a record, human-in-the-loop is the default rather than an option somebody remembers to add.

Without FlowRunner

Orders worked out of the back office Somebody opens the shop admin, prints the slips and types tracking numbers back in one order at a time

Stock overwritten by whichever feed ran last Two systems each set an absolute number, and the later one wins whether or not it was the better number

Unsubscribe requests handled by hand Somebody removes an address in the interface, and no record is kept of which kind of request it actually was

With FlowRunner

Documents fetched and delivered Picking slips, delivery slips and invoices come out of the authenticated API and land where the person who needs them will look

Stock moved as deltas Increase and Decrease are applied by the platform, so two concurrent feeds add up rather than overwriting one another

Consent treated as two separate acts Suppressing an address and erasing it are different requests with different consequences, and a person says which one this is

Use Case Scenarios

An order that reaches the warehouse and comes back with a number

The On Order Event trigger fires on a new order. The agent calls Get Order for the lines and the shipping records, and Download Picking Slip to pull the PDF the warehouse works from into file storage. The slip goes out with the order reference through Gmail, or straight to the third party warehouse. A label is bought through Shippo and Ship Order writes the tracking number back, one entry per parcel against that parcel's own shipment record rather than against the order. Set Order Status then moves the order along, which is what the customer sees when they check.
Two stock feeds that do not fight each other

A supplier price and stock file lands in Google Sheets each morning while a marketplace channel writes its own movements throughout the day. The agent reads the file and calls Update SKU Stock with Increase or Decrease rather than Replace, so the two feeds accumulate instead of overwriting. Prices go through Update Product, with the images, tags and attributes read first and sent whole, since the platform writes each of those arrays complete. When the On SKU Event trigger reports a SKU at zero, the agent alerts the buying team in Slack and calls Set Product Visibility to mark the product unavailable rather than hiding it, which keeps the page and its reviews alive for when stock returns.
Customers synced into marketing, consent included

The On Customer Event trigger fires when a customer account is created. The agent reads the record with Get Customer, including the newsletter opt in flag, and creates or updates the profile in Klaviyo, subscribing only when the flag says so. A nightly pass runs List Customers with Updated Since for the incremental sync, using the turnover and valid order count that arrive on the list row so segmenting by value needs no follow up call. When an unsubscribe comes back from the marketing platform, Set Newsletter Opt In writes it to the shop with Unsubscribe, so the shop and the marketing platform agree in both directions.

Human-in-Loop Highlight

There are two ways to stop emailing somebody through this connector and they are not variations of the same thing. Set Newsletter Opt In with Unsubscribe records that this address has opted out, which is the evidence a shop needs to show it honored the request. Delete Newsletter Subscriber removes the address from the list entirely, and with it any record that it was ever there or ever asked to leave. An agent reading an inbound request cannot reliably tell an unsubscribe from an erasure request, because customers write both the same way, and the second one is what the first one looks like once it has been carried out wrong. So the agent does the suppression, which is safe and reversible, and stops on the rest: "marie@example.fr asks to be removed. Suppressed on the shop and in Klaviyo. Their message also asks that you delete their data. Erase the subscriber record, which removes the proof of the opt out, or leave it suppressed?" A person answers. The agent is fast at the part that is safe either way, and silent on the part that is not.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

75 actions

Shop and Account

List Shops Returns every shop the WiziShop account owns, with the id every other operation in this service needs. This is the connection test: it needs nothing but valid credentials, and the account id is read straight out of the sign in response.
List User Shops Returns the shops one WiziShop user has access to, which is not necessarily every shop on the account. Use List Shops for the account wide view; this one answers "what can this person see".
Get Shop Returns a shop's settings: its name, locale, currency, plan, domain, postal address, tax configuration, template and open or closed status. is_dropizi distinguishes a Dropizi dropshipping store from a standard WiziShop one, and currency is what every money field on that shop is denominated in.
Rename Shop Changes a shop's name. The name is the only field this route accepts. WiziShop's own note on it reads "just patch the name for now", so the domain, locale, currency, address and tax settings cannot be changed through the API and have to be edited in the WiziShop back office.
Update User Changes a WiziShop user's first name, last name or email address. This edits the person signing in, not a customer of the shop; Update Customer records live under the Customers category.

Orders

List Orders Returns a page of orders with their public id, customer name, product count, total, currency, status code and tag. Order ID greater than is what makes an incremental sync possible: keep the highest id you have seen and pass it back, and only newer orders come back.
Get Order Returns the full order: totals with and without tax, shipping and discount lines, payment mode and transaction number, billing and shipping addresses, every shipment with its tracking number, and each line's SKU, variations and customizations.
Get Order Stats Returns the order count, turnover, total products ordered and the number of orders still awaiting preparation between two dates. The cheapest daily reporting call in this service: one request instead of paging the whole order list.
Set Order Tag Writes the free text tag on an order, which List Orders can then filter on. An order has one tag and this replaces it, so a flow that adds a second label overwrites the first.
Create Order Records an order that was taken somewhere else, with its billing address, shipments, lines, variations, customizations, services, discounts and status history. WiziShop labels this route [Alpha] in its own documentation, so treat it as unstable and verify the result before building a fulfillment flow on it.
Get Store Credit Returns one store credit with its total amount, the order it was raised against, the customer, the reason text and the line by line breakdown of what was credited.

Order Documents

Download Invoice Fetches the order's invoice PDF and stores it in FlowRunner file storage, returning a URL a later step can attach to an email or push to a drive.
Download Delivery Slip Fetches the order's delivery slip PDF, the document that travels in the parcel, and stores it in FlowRunner file storage, returning a URL.
Download Picking Slip Fetches the order's picking slip PDF, the warehouse document listing what to pull off the shelves, and stores it in FlowRunner file storage, returning a URL.

Order Status

Set Order Status Moves an order into one of WiziShop's eleven built in statuses. WiziShop publishes one route per status rather than a status field, and this operation is all of them behind a single picker, so a flow does not need eleven near identical blocks.
Ship Order Moves an order to shipped and records a tracking number per shipment. The shipment ID is not the order ID: each entry's shipping_id is the id of one of the order's own shippings entries, which Get Order returns, so a multi parcel order needs one entry per parcel.
Set Order Custom Status Moves an order into one of the shop's own custom order states, the ones created with Create Order Custom State. Custom states are how a merchant models a step WiziShop has no built in status for, such as "awaiting supplier" or "engraving".
List Order Custom States Returns the shop's own order states with their numeric state code, admin title, storefront title and editable flag. Read editable before deleting: WiziShop refuses to delete a state that is not editable, and the refusal names nothing useful.
Create Order Custom State Registers a new custom order state with a separate title for the back office and for the storefront. The admin title is unique: WiziShop refuses a second state with the same title_admin, so a flow that re-runs must check List Order Custom States first rather than assuming a create is idempotent.
Update Order Custom State Renames a custom order state in the back office, on the storefront, or both. The admin title stays unique, so renaming onto another state's name is refused.
Delete Order Custom State Removes a custom order state from the shop. It only works when the state's editable flag is true, which List Order Custom States reports; a state WiziShop marks non editable cannot be removed through the API.

Products

List Products Returns a page of products with their id, SKU, label, stock, weight and status. This is the catalog index, not the full record: descriptions, prices, images, attributes and meta come back only from Get Product.
Get Product Returns the whole product record: descriptions, brand, EAN13 and isbn, tax, weight, prices and reductions, images, attributes with their per option SKUs and stock, customizations, cross selling, meta title and description, and shipping overrides.
Create Product Adds a product to the catalog with its category, SKU, descriptions, pricing, tax, stock, images and variations. WiziShop labels this route [beta], so verify the created record before wiring it into a bulk import.
Update Product Changes a product's category, descriptions, pricing, stock, images, variations, meta or shipping overrides. WiziShop labels this route [beta]. Sending an array replaces it: Images, Tags, Other Categories and Attributes are written whole, so a call that sends one image leaves the product with one image.
Delete Product Removes a product from the catalog. This is not hiding a product: to take something off sale while keeping its record, its reviews and its URL, use Set Product Visibility with Hidden instead.
Set Product Visibility Publishes, hides or marks a product unavailable, without touching anything else about it. Unavailable is the middle state: the product page stays reachable and indexed, but nothing can be added to a basket, which is what an out of stock item usually wants rather than being hidden outright.
List Category Products Returns the ids of every product in a category. It returns IDS only, not product records, so a flow that needs names or prices has to follow up with Get Product per id.

Inventory

List SKUs Returns a page of stock keeping units, products and variations alike, with stock, EAN13, status and timestamps. This is the stock feed: Updated Since and Updated Until turn it into an incremental sync, and type tells a product row apart from a variation row, which List Products cannot do.
Get SKU Returns one stock keeping unit with its stock, label, purchasing price, brand, weight, barcode and timestamps, and whether it is a product or a variation.
Update SKU Stock Sets, raises or lowers the stock on one SKU. This is the right route for a warehouse feed, because Increase and Decrease are applied by WiziShop rather than by the flow, so two concurrent updates do not overwrite each other the way a Replace would.

Brands

List Brands Returns a page of the shop's brands with their id, name and URL slug. The Products operations take a brand name while these take a brand id, so this is the lookup between the two.
Get Brand Returns one brand with its name, URL slug and logo image URL.
Create Brand Adds a brand to the shop, optionally with a logo. WiziShop derives the URL slug from the name, so the created record tells you the slug the storefront will use.
Update Brand Renames a brand or changes its URL slug or logo. Changing the slug breaks existing links to the brand page.
Delete Brand Removes a brand from the shop. WiziShop does not report what happened to the products that carried it, so check List Products filtered on that brand first if the catalog depends on it.

Product Filters

List Product Filters Returns the shop's storefront filters with the facets (the selectable values) inside each one. A filter is the heading a shopper sees in the left hand column, such as Material or Size, and a facet is one option under it.
Create Product Filter Adds a new storefront filter heading. It starts with no facets, so it does nothing on the storefront until Create Facet adds values to it.
Rename Product Filter Changes a filter's heading. The route only accepts the label, so a filter's facets are edited with the facet operations rather than here.
Delete Product Filter Removes a filter and every facet under it. This also detaches the filter from every product that used it, so the facet values recorded against those products go with it.
Get Product Filters Returns the filters and facet values recorded against one product. Call this before Set Product Filters: that operation replaces the set, so this is where the current list comes from.
Set Product Filters Writes the complete set of filters and facet values on a product. WiziShop's own word for this route is "replace": it is not an add.
Create Facet Adds one selectable value under an existing filter, for example Cotton under Material. A new facet has no position until Reorder Facets sets one.
Delete Facet Removes one selectable value from a filter, and with it that value on every product that carried it.
Reorder Facets Sets the order the filter's values appear in on the storefront. Send every facet ID: the array is the whole order, so a facet you leave out has no defined position afterwards.
List Facet Variants Returns the product variants and their options that can be attached to a facet, each with a checked flag showing whether it already is.
Assign Facet Variants Attaches product variant options to a facet, so that choosing that facet on the storefront selects those variants. WiziShop states plainly that this adds: variants already attached are left alone, so you do not have to resend the whole set.
Unassign Facet Variants Detaches product variant options from a facet, leaving every other attachment in place. It is a POST rather than a DELETE, because it takes a list in its body.

Customers

List Customers Returns a page of customers with their name, gender, email, registration date, lifetime turnover, valid order count, loyalty points and newsletter opt in.
Get Customer Returns one customer with their contact details, birthdate, newsletter opt in, lifetime turnover, valid order count and both stored addresses. The list row and this record spell the addresses differently, so a flow reading billing_address should take it from here.
Create Customer Registers a customer account on the shop with a password and optional shipping and billing addresses. WiziShop labels this route [Alpha], so verify the created record before wiring it into a migration.
List Newsletter Subscribers Returns a page of email addresses subscribed to the shop's newsletter, with the date each one signed up. This is not the customer list: someone can subscribe to the newsletter without ever creating an account, and a customer's own optin flag lives on the customer record instead.
Set Newsletter Opt In Subscribes or unsubscribes one email address from the shop's newsletter. Unsubscribe is a real instruction and not an empty one: WiziShop encodes it as the path segment 0, which a naive request builder would drop as falsy and turn into no change at all.
Delete Newsletter Subscriber Removes an email address from the shop's newsletter list entirely. This is erasure, not unsubscribing: the record goes, so there is no longer any evidence that the address ever opted out.
Set SMS Opt In Subscribes or unsubscribes a customer from the shop's SMS marketing. This one takes a customer ID, not an email address, which is the opposite of the newsletter routes.

Reviews

List Shop Comments Returns a page of reviews left about the shop itself, with the author, rating, content and date, plus a total_note carrying the shop's average rating.
Create Shop Comment Records a review of the shop, which is how reviews collected somewhere else are imported into WiziShop. Valid defaults to off and controls publication: a review created without it stays unpublished until a moderator approves it, so a bulk import that expects reviews to appear on the storefront has to set it deliberately.
List Product Comments Returns a page of reviews left on one product, with the author, rating, content and date, plus a total_note carrying that product's average rating.
Create Product Comment Records a review on one product, which is how reviews collected elsewhere are imported. Valid defaults to off and controls publication, so an imported review stays invisible on the storefront until it is set.

Storefront Scripts

List Scripts Returns the code snippets injected into the storefront, each with the pages it runs on, where in the document it sits, and which devices it targets.
Create Script Injects a code snippet into the storefront, scoped to a set of pages, a position in the document and a device class.
Update Script Changes a storefront script's name, target pages, position, device class or code. The change is live immediately on the shop's storefront. Avoid editing a script whose id is negative: those belong to WiziShop's own integrations.
Delete Script Removes a code snippet from the storefront. Deleting a tracking or advertising tag stops the data it collected without any other warning, so confirm what a script is before removing it.

Webhooks

List Webhooks Returns the shop's webhooks with their endpoint URL, the resources they watch, their retry and timeout settings, and their delivery secret. The secret field is the verification value in cleartext, and WiziShop sends that same string back on every delivery in the WiziShop-webhook-secret header.
Get Webhook Returns one webhook with its endpoint, resources, retry policy and delivery secret. The secret comes back in cleartext, because that is the only form WiziShop has of it.
Create Webhook Registers an endpoint that WiziShop will POST to when an order, a SKU or a customer changes. Resources are not event names: order, sku and customer are the entire vocabulary, and the verb arrives inside the payload as event.op, one of INSERT, UPDATE or DELETE.
Update Webhook Changes a webhook's endpoint, the resources it watches, its description or its retry and timeout settings. The resources array is replaced, not merged, so a call that sends one resource stops the deliveries for the others.
Delete Webhook Removes a webhook, stopping its deliveries immediately. Do not delete a webhook that a running FlowRunner trigger created: the trigger cleans up its own webhooks when the flow stops, and removing one by hand leaves the trigger silent with no error anywhere.
List Webhook Logs Returns a page of delivery attempts for one webhook, each with the resource, the HTTP status your endpoint returned, whether it was delivered, and the request and response bodies.
Redeliver Webhook Event Sends one past event to the webhook's endpoint again, which is how a delivery that failed while your endpoint was down is replayed.

Triggers

3 triggers

Event Triggers

On Order Event Fires when an order is created, changed or deleted on the chosen shop. WiziShop subscribes to the order resource as a whole rather than to named events, and reports what happened inside the payload, so the Operation setting filters deliveries here rather than narrowing the subscription. A status change, a tag change and a brand new order all arrive as the same kind of delivery, so compare the record against your own copy to find out what moved.
On SKU Event Fires when a SKU is created, changed or deleted on the chosen shop, which is WiziShop's stock and variation feed. This is the trigger that catches a stock movement, including the drop caused by a sale, so it is what an out of stock alert or a supplier reorder flow watches. It also fires on the flow's own Update SKU Stock calls, so a two way sync needs a guard against feeding itself.
On Customer Event Fires when a customer record is created, changed or deleted on the chosen shop. Created is the signal a welcome sequence or a CRM sync waits for. A newsletter subscriber who never opened an account is not a customer, so a subscription on its own does not fire this.

Frequently Asked Questions

What can FlowRunner do with WiziShop?

FlowRunner agents can run List Shops, List User Shops, and Get Shop in WiziShop, plus 72 more actions.

Does connecting WiziShop to FlowRunner require OAuth?

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

Can WiziShop trigger a FlowRunner workflow automatically?

Yes. WiziShop supports 3 triggers that can start a FlowRunner workflow automatically.

Start building with WiziShop

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us