3dcart

3dcart, now sold as Shift4Shop, is a hosted storefront platform with a mature REST API. Agents sync products, stock and prices from an ERP, import orders from other channels, manage customers, promotions and returns, and react to store webhooks in real time.

1 trigger 105 actions API key available

3dcart website Platform Documentation Capability data verified 2026-08-26

On Store Event fires for an order event on the store

Get Order reads the record back, because the store does not sign its webhook deliveries

The agent resolves the order's numeric status against the store's own status list rather than a hard coded number

Update Order Shipment writes the tracking code and shipped date onto the right shipment

Update Order moves the order into the store's shipped status

The shopper gets tracking, and the fulfillment channel gets the summary

A service agent decides what goodwill, if any, a delayed or short order is owed

What This Integration Enables

3dcart, sold today as Shift4Shop, belongs to a particular kind of merchant: the one for whom the storefront is not one system among many but the system. Wholesale price tiers are customer groups. Drop ship suppliers are distributors with a notification flag. Store credit is a gift certificate code. Returns, checkout questions, promotions and the store's own configuration all live behind the same API. That makes the connector unusually wide, and it makes the automation question different from the one a large retailer asks. It is not how to move data between systems. It is how much of the back office a merchant can hand to agents.

FlowRunner agents work that whole surface. They sync stock and prices through the cheap inventory projection rather than whole product records, import orders taken on other channels, write tracking onto the correct shipment of a multi box order, maintain customer groups and drop ship suppliers, build live carts from an external experience and hand the shopper to the store's own checkout, and react to store events through a webhook backed trigger. Because the store is also the ledger of what shoppers are owed, the human-in-the-loop gate on this connector sits on the operations that move a shopper's money, not on the ones that move data.

Without FlowRunner

The store is the back office Wholesale tiers, drop ship suppliers, promotions and store credit all live here, and all of them are maintained by hand

Tracking arrives late or not at all Numbers come back from a carrier or a 3PL and sit in an inbox until someone types them into the right shipment

Stock reconciled by exporting everything Checking prices and quantities means pulling whole product records for a catalog that only needed its stock figures

With FlowRunner

The store is a system agents can run Catalog, orders, customers, groups, suppliers, promotions and credit are all reachable from the same workflow

Tracking is written where the shopper sees it The shipment record gets the code and the shipped date as soon as the warehouse reports it

Stock syncs on the cheap projection The inventory view returns SKU, price and stock without whole product documents, so a large catalog stays in step

Use Case Scenarios

Orders out to fulfillment, tracking back in

An order event arrives on the trigger. Because deliveries are not signed by the store, the agent reads the record back with Get Order before acting on anything in the payload. The order is pushed into ShipBob for fulfillment, and when a shipment leaves, the agent calls Update Order Shipment with the tracking code and shipped date, which is what makes tracking visible to the shopper rather than merely recorded. Multi box orders are handled properly: Add Order Shipment creates the second shipment and Update Order Item assigns the lines that belong to it, so a split delivery shows two tracked parcels instead of one confusing one. A parallel workflow polls ShipStation for anything dispatched outside the main path.
Stock and prices from the source of truth

The ERP or the supplier sheet holds the real numbers. On a schedule the agent reads List Product Inventory, which returns catalog id, SKU, name, cost, price, sale price and stock without pulling whole product documents, so a catalog of thousands reconciles cheaply. Differences are written back through Update Products in batches, and the agent reads the response carefully because that route can report partial success with some records applied and others rejected. For products that track stock by size or color, Update Product Advanced Option adjusts the individual combination rather than the parent record. A daily stock report lands in Google Sheets for the warehouse team.
The wholesale and drop ship back office

A new wholesale account is approved. The agent creates the customer, assigns them to the customer group that carries the right price level, and saves their delivery addresses so checkout does not ask twice. On the supply side, Create Distributor registers a drop ship partner with the notification flag turned on, which is what makes the store email that supplier a purchase order when an order containing their products lands. Customer group membership is exported to Klaviyo so the wholesale segment gets its own email treatment, and the day's orders post into QuickBooks Online as invoices.

Human-in-Loop Highlight

Update Gift Certificate sets the balance rather than adding to it. That single detail turns a routine goodwill top up into the most dangerous call in this connector: writing 25 onto a certificate that currently holds 180 does not make it 205, it destroys 155 of a shopper's money, and Delete Gift Certificate destroys the remainder outright. There is no undo for either. So the service workflow does the arithmetic and stops. The agent reads the current balance with Get Gift Certificate, works out the resulting figure, and asks: "Order 20416 shipped nine days late. This shopper holds certificate WELCOME-4471 with 180.00 remaining. Approving a 25.00 credit will write a new balance of 205.00, replacing the old one outright. Approve 25.00, choose a different amount, or decline?" A person names the number. What the agent contributed was the balance lookup, the corrected total and the warning that this operation overwrites; what it did not do was decide on its own how much of the store's money a delayed parcel is worth.

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

105 actions

Products

List Products Lists catalog products filtered by SKU, name, cost, price, stock, last update window and any of the store's catalog flags. Every flag filter has three states, so leaving one blank is not the same as turning it off.
Get Product Reads a single product by catalog id, including its nested stock and pricing section, category and distributor lists, images, option sets and advanced options.
Create Product Creates a product. SKU, name, price, cost and stock live inside the product's nested section rather than at the top level, and this operation takes them as ordinary parameters and nests them correctly.
Update Product Updates one product by catalog id, sending only the fields you set. This is the single record route and takes an object, unlike its bulk sibling.
Update Products Updates many products in one request, each identified by the catalog id inside its own object. The route can report partial success, so this operation returns succeeded, failed and a failures list rather than a bare flag.
Delete Product Permanently deletes a product from the catalog. This cannot be undone.
List Product Inventory Returns the stock and pricing section only for every product: catalog id, SKU, name, cost, price, sale price and stock. This is the operation an inventory sync should use, because it gives a reconciliation exactly what it needs without whole product documents.
Get Product Inventory Returns the same projection for a single product, which is the cheapest way to read one item's current stock and price.
List Category Products Lists the products assigned to one category, with the same filters as the main product list.
List Manufacturer Products Lists the products assigned to one manufacturer, with the same filters as the main product list.
List Distributor Products Lists the products a distributor supplies. Useful for building a drop ship purchase order, since a distributor here can be flagged as a drop shipper.
List Product Categories Lists the categories a single product is assigned to. This is the read side of the category list field on the product write operations.
List Product Distributors Lists the distributors assigned to a product, with each supplier's own cost and part number for it.

Product Images

List Product Images Lists the gallery images attached to a product with their captions and sort order. The main product image is a field on the product record itself rather than part of this gallery.
Add Product Image Attaches a gallery image to a product. The store takes a file path rather than an upload, so the image must already exist in the store's assets folder and this call records the path, caption and position.
Update Product Image Changes the path, caption or sort position of one gallery image.

Product Options and Discounts

List Product Options Lists a product's option sets, such as size or color, each with its selectable options and their price adjustments.
Add Product Option Set Creates an option set on a product, optionally with its options in the same call. A set with no options inside it never appears on the storefront.
Update Product Option Set Changes one of a product's option sets, including replacing the options inside it.
Add Product Option Adds a single choice to an option set that already exists. Use this rather than the set level update when appending one option, because sending a full option list replaces the whole set.
List Product Advanced Options Lists the per combination rows that carry their own SKU suffix, cost, price, weight and stock. For a product that tracks inventory by option, this is where the real stock numbers live.
Add Product Advanced Options Adds advanced option rows to a product. Unlike every other create here this route takes an array, so several combinations are added in one call with one status per row.
Update Product Advanced Option Updates one advanced option row by its code. This is the operation that adjusts stock for a single size or color combination.
List Product Discounts Lists the quantity break discounts on a product, each pairing a threshold quantity with a discounted price.
Add Product Discount Adds a quantity break discount, so ordering at or above a threshold switches to a lower unit price.

Orders

List Orders Lists orders filtered by order date, last update window, status, invoice number or range, invoice prefix and billing email. The store expects its own date format rather than the ISO form, and this connector converts for you.
Get Order Reads one order by its internal order id, with the full item, shipment and transaction lists, promotions and checkout questions. The order id is not the invoice number the shopper sees.
Create Order Creates an order in the store, which is how an order taken on another channel is imported. By default this runs the store's full order processing, so stock is decremented, reward points are awarded and the new order email is sent, unless processing is bypassed deliberately.
Update Order Updates one order by id. Changing the order status is what most fulfillment workflows need, since a store's fulfillment states are just its order statuses.
Update Orders Updates many orders in one request, each identified by the order id inside its own object. Like the bulk product route it can report partial success, so this operation reports succeeded, failed and a failures list.

Order Items and Shipments

List Order Items Lists the line items on an order with quantity, unit price, chosen options, warehouse location and the shipment each item belongs to.
Add Order Item Adds a line item to an existing order. The store does not recalculate the order total from its items, so adjust the order amount separately if the addition should change what the shopper owes.
Update Order Item Updates one line item, addressed by its item index rather than by the product's catalog id. Also the operation that assigns a line to a particular shipment.
List Order Shipments Lists the shipments on an order, each with its destination, method, cost, weight, tracking code and shipped date. One order can hold several shipments, and every line belongs to one of them.
Add Order Shipment Adds a shipment to an order, which is how a split delivery or a second box is recorded. Adding it does not move any line into it, so assign the items afterward.
Update Order Shipment Sets the tracking code and shipped date on a shipment. This is the fulfillment write: it is what turns a paid order into a shipped one for the shopper, and pairing it with the shipment's own status is how a partial shipment is recorded.

Order Payments, Questions and Notices

List Order Transactions Lists the payment gateway transactions recorded against an order, with amount, type, approval code, response text and whether it was captured.
Add Order Transaction Records a payment gateway transaction against an order. This records history and does not take a payment: no money moves and no gateway is called, so use it to reconcile a charge that happened elsewhere.
Update Order Transaction Updates one recorded transaction, usually to flip the captured flag on after an authorization was settled outside the store.
List Order Questions Lists the custom checkout questions and answers on an order, which is where anything the store asked beyond the standard fields, such as a delivery date or a gift message, is kept.
Add Order Question Records a question and answer against an order, so a note captured outside checkout lands in the same place the store's own checkout answers live.
Update Order Question Updates one recorded question or its answer on an order.
Send Gift Card Recipient Email Sends the store's gift card email to the recipients named on a gift card line of an order. The store takes the order item itself here rather than a recipient list, so pass the line as it appears on the order.

Order Statuses

List Order Statuses Lists every order status the store defines, with its id, display text, sort order and whether shoppers see it. Statuses are configurable per store, so a workflow reads them rather than hard coding a number.
Get Order Status Reads one status by id, which is how a numeric status on an order becomes the text a person recognizes.

Customers

List Customers Lists customers filtered by email, name, city, state, country, phone and last update window. Filtering on the last update window is what makes an incremental sync to an email platform possible.
Get Customer Reads one customer by id with billing and shipping addresses, customer group, mailing list flag and store credit balance.
Create Customer Creates a customer account. The store does not enforce a unique email here, so an import should look the address up first or it will create duplicates.
Update Customer Updates one customer by id, sending only the fields you set. This is the single record route and takes an object.
Update Customers Updates many customers in one request, each identified by the customer id inside its own object. It can report partial success, so this operation returns succeeded, failed and a failures list.
Delete Customer Permanently deletes a customer account. Turning the account off with an update is the reversible alternative and keeps the shopper's order history attached to a real account.

Customer Addresses

List Customer Addresses Lists the entries in a customer's address book, meaning the extra delivery addresses beyond the default on the account.
Get Customer Address Reads one address book entry by its id.
Add Customer Address Saves an extra delivery address against a customer so it can be chosen at checkout without being retyped.
Update Customer Address Updates one address book entry, sending only the fields you set.

Customer Groups

List Customer Group Customers Lists the customers in one group, with the same filters as the main customer list. This is how a price tier or wholesale segment is exported to an email tool.
List Customer Groups Lists the store's customer groups with their price level, minimum order, tax treatment and registration settings. The price level is what maps a wholesale shopper to the product's tiered prices.
Get Customer Group Reads one customer group by id, including its price level and registration message.
Create Customer Group Creates a customer group, which is this platform's mechanism for wholesale tiers, tax exempt segments and gated pricing. Allowing registration without auto approval means applications wait for a person.
Update Customer Group Updates one group by id. Changing the price level changes what every member of the group pays immediately.
Delete Customer Group Permanently deletes a group. Its members survive but lose the group's price level and tax treatment, so read the membership first.

Manufacturers

List Manufacturers Lists the brands defined in the store, each with its logo, website and storefront page settings.
Get Manufacturer Reads one manufacturer by id, including its logo path, page title and any storefront redirect.
Create Manufacturer Creates a brand that products can be assigned to. A product references a manufacturer by id, so create the brand before the products that belong to it.
Update Manufacturer Updates one manufacturer by id, sending only the fields you set.
Delete Manufacturer Permanently deletes a manufacturer. Products that referenced it keep the id and are left pointing at a brand that no longer exists, so reassign them first.

Distributors and Drop Shipping

List Distributors Lists the store's distributors filtered by company, email, city, state, country or phone. A distributor here is also a drop shipper, and the flags on each record decide whether the store emails a purchase order when a matching order lands.
Get Distributor Reads one distributor by id with contact details, drop ship flag and the purchase order notification templates the store sends it.
Create Distributor Creates a distributor or drop shipper. Turning on the drop ship and new order notification flags together is what makes the store email that supplier automatically, which is the whole drop ship workflow.
Update Distributor Updates one distributor by id, sending only the fields you set.
Delete Distributor Permanently deletes a distributor. Products that listed it lose the supplier link, and any drop ship notification the store was sending them stops.

Live Carts

Create Cart Creates a live cart on the store and returns its order key. This is how an external experience hands a shopper to the store's own checkout: build the cart elsewhere, then send the shopper in with the key.
Get Cart Reads a live cart by its order key, including items, quantities and any addresses captured so far.
Update Cart Updates a live cart's billing and delivery details. Filling these in before the handoff is what lets the shopper skip the address forms.
Delete Cart Deletes a live cart and everything in it. A shopper holding the order key will find the cart gone, and this cannot be undone.
Add Cart Item Adds a catalog product to a live cart. Options are sent as pairs of option set and option, which is why a product with required options needs its option sets read first.
Update Cart Item Changes the quantity of one line in a live cart. Quantity is the only field this route accepts, so changing a product or its options means removing the line and adding a new one.
Delete Cart Item Removes one line from a live cart.

Promotions

List Promotions Lists the store's promotions with coupon codes, date windows, discount rules and usage counters. The promotion model is wide and mostly numeric flags, so read one before trying to copy its shape.
Get Promotion Reads one promotion by id with its full rule set, coupon code, usage limits and redemption count.
Create Promotion Creates a promotion, optionally with a coupon code. The discount size and its kind are separate fields, so a ten percent discount is the number ten with the percentage flag on.
Update Promotion Updates one promotion by id. Turning it off is the safe way to stop a live coupon without losing its redemption history.
Delete Promotion Permanently deletes a promotion and its redemption history. Disabling it is the reversible alternative.

Gift Certificates

List Gift Certificates Lists gift certificates filtered by note text or by issued amount and remaining balance ranges. Filtering on a balance above zero is how outstanding certificate liability gets reported.
Get Gift Certificate Reads one certificate by its code, including the issued amount and remaining balance. Certificates are addressed by code rather than by a numeric id.
Create Gift Certificate Issues a certificate for a fixed amount, which is how a service workflow makes a goodwill credit spendable at checkout. The code is yours to choose and must be unique, so generate one rather than reusing a customer identifier.
Update Gift Certificate Updates a certificate by its code. Sending an amount sets the value rather than topping it up, so read the current balance first. The operation this page's human gate exists for.
Delete Gift Certificate Permanently deletes a certificate. Any remaining balance is destroyed with it and a shopper holding the code is refused at checkout.

Store and Returns

Get Store Settings Reads the store's configuration in its three sections. Useful for reading currency, weight unit and contact details so a workflow formats amounts the way the storefront does.
Update Store Settings Writes live storefront settings. The store takes the whole configuration object rather than a patch, so read it, change what you need in that object and send it back, because a partial object risks clearing what it omits.
Get Version Returns the software version the store is running. It takes no parameters and touches no store data, so a successful call proves all three credentials at once.
List RMAs Lists return merchandise authorizations filtered by status, reason, method, catalog id, SKU or date range. The status, reason and method filters take numeric ids the vendor does not publish, so read an existing return to learn which numbers a store uses.
Get RMA Reads one return authorization by id, with its order reference, status, reason and customer details.
List RMA Items Lists the lines a shopper is returning under one authorization, with SKUs and quantities. This is what a restocking workflow reads before adjusting stock.

Webhooks

List Webhooks Lists the webhooks registered on the store, filtered by name, URL, enabled flag, format or date ranges. This includes the registrations FlowRunner's own trigger created, which are named after the trigger that owns them.
Get Webhook Reads one webhook by id, with its URL, event type, format, enabled flag and timestamps.
Create Webhook Registers a webhook so the store posts an event to a URL you control. The event type is an undocumented integer, so the parameter is backed by a live read of the store's own event catalog rather than a hard coded map.
Update Webhook Updates a webhook by id. Turning it off is how a delivery endpoint is taken out of service without losing its registration.
Delete Webhook Removes a webhook registration so the store stops posting that event. Do not delete one named after a FlowRunner trigger by hand, because stopping the flow removes it and deleting it here leaves the trigger receiving nothing.
List Webhook Events Lists the store's webhook event catalog, pairing each event's integer with its name. This is the only place those numbers are published, so it is the sole authority on which number means which event.

Triggers

1 triggers

Event Triggers

On Store Event Fires when the store reports the event you subscribe to, such as an order or product change. The event list is read live from the store, because events are identified by an integer published nowhere else. Deliveries are not signed by the vendor, so the trigger accepts only deliveries arriving on its own unguessable callback URL, and a workflow should read the record back before acting on it.

Frequently Asked Questions

What can FlowRunner do with 3dcart?

FlowRunner agents can run List Products, Get Product, and Create Product in 3dcart, plus 102 more actions.

Does connecting 3dcart to FlowRunner require OAuth?

No. 3dcart connects to FlowRunner with an API key, no OAuth flow required.

Can 3dcart trigger a FlowRunner workflow automatically?

Yes. 3dcart supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with 3dcart

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us