--- title: "AmeriCommerce (Cart.com) Integration" description: "AmeriCommerce by Cart.com is a multi-store online storefront platform. Agents push orders into a warehouse or ERP, write shipments and tracking back, keep stock in step by SKU, and manage the catalog, customers and checkout pipeline." url: https://flowrunner.ai/integrations/americommerce date_modified: 2026-09-04T19:26:11-07:00 --- # AmeriCommerce (Cart.com) [E-commerce](https://flowrunner.ai/integrations/category/e-commerce) AmeriCommerce by Cart.com is a multi-store online storefront platform. Agents push orders into a warehouse or ERP, write shipments and tracking back, keep stock in step by SKU, and manage the catalog, customers and checkout pipeline. 115 actions · API key · available [AmeriCommerce (Cart.com) website](https://cart.com/) · [Platform Documentation](https://github.com/AmeriCommerce/rest-api) · Capability data verified 2026-08-26 1. An order arrives from a marketplace, a phone sale or an EDI feed, already priced and already paid 2. Agent reads the buyer, the lines, the totals and the payment reference from the source system 3. Get Inventory confirms stock for each line by SKU, GTIN or product id 4. List Customers resolves the buyer against the store, and Create Customer adds them if this is a first order 5. Create Order Address writes the billing and shipping records the imported order will point at 6. Agent posts the assembled order, its totals and its payment status to the operations channel 7. An operator confirms the order is recorded as already settled rather than run through checkout again ## What This Integration Enables AmeriCommerce is a storefront you own outright, and the connector inherits that. There is no shared vendor API host: every call goes to the merchant's own SSL domain, the token is minted in the store admin console with the scopes it needs, and the rate limit is shared with every other app the merchant has installed. That last detail shapes how a flow should be written more than any feature does. FlowRunner agents read orders, carts, products, customers and inventory with filtering and nested expansion so one call does the work of five, and reach the long tail of the store's roughly seventy resources through a generic record surface rather than waiting for a named operation. The write side is where judgment matters. Agents import orders that were priced somewhere else, adjust stock relatively so concurrent events cannot overwrite each other, push a supplier feed into the catalog with tiered pricing and images, and drive the cart pipeline that rates carriers and evaluates discounts. FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) discipline is the default around all of it: agents assemble, price and reconcile at machine speed, and the operation that takes money from a real card stops and asks first. ### Without FlowRunner **Orders retyped by hand**: Marketplace and phone orders reach the storefront through a person with a spreadsheet open **Stock agreed nowhere**: The storefront, the warehouse and the accounting system each hold a different number for the same SKU **Call budget spent blindly**: Every integration on the store draws from one shared rate limit, and nobody knows which one exhausted it ### With FlowRunner **Orders arrive as records**: Imports run continuously, with addresses, lines and settlement written in the order the store expects **One number, adjusted not overwritten**: Stock moves by relative adjustment, so two events landing together cannot cancel each other out **Reads batched on purpose**: Bulk reads and nested expansion replace loops of single lookups, so the flow leaves budget for the merchant's other tools ## Use Case Scenarios ### Orders priced elsewhere become storefront orders A sweep runs on a schedule, filtering List Orders on the ordered date since the last run and expanding items, payments and shipments in the same call so the store's shared rate limit is not spent on a loop of single reads. New orders go out to the warehouse, where [ShipBob](https://flowrunner.ai/integrations/shipbob) picks them up as fulfillment jobs. When each one ships, Create Order Shipment writes the tracking number back onto the storefront order so the buyer's account page tells the truth. A second pass hands the day's orders to [QuickBooks Online](https://flowrunner.ai/integrations/quickbooks-online) as invoices and calls Create Order Payment to record the settlement back against the order. The agent moves records between systems; nobody rekeys an order number. ### One stock number, adjusted rather than overwritten The product master lives in [Airtable](https://flowrunner.ai/integrations/airtable), and the physical count lives in the warehouse. The agent reads the master, pushes names, descriptions and tiered pricing with Update Product and Create Product Price, and keeps stock in step with Add Inventory and Remove Inventory rather than Set Inventory, because a relative adjustment cannot silently discard a storefront order that landed in the same second. Get Inventory Settings is read first, since whether stock comes down at order time or at ship time decides whether the two systems will ever agree. When a SKU falls below its reorder point, the shortfall appends to a sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) and posts to the buying channel in [Slack](https://flowrunner.ai/integrations/slack). ### A quote that converts without charging twice B2B quotes go quiet. A nightly pass uses List Quotes to find the ones with no movement, adds each buyer to a nurture list with [Klaviyo](https://flowrunner.ai/integrations/klaviyo), and issues a single use code with Create Coupon Code so the follow up carries something concrete. When a buyer accepts, the agent builds the order through the cart pipeline: Create Cart, Add Cart Items, Calculate Cart Shipping, Set Cart Shipping Method, Apply Cart Coupon Code, then Get Calculated Cart to force a full recalculation of price, freight and discount. It posts that final total to the account owner and stops. Place Cart Order runs only after a person has read the number. ## Human-in-Loop Highlight There are two ways to put an order into AmeriCommerce and they look identical afterwards. Create Order records an order that was priced and paid somewhere else and charges nothing. Place Cart Order runs the checkout and takes the payment, and it is the only operation in these 115 that touches a card. Nothing here refunds, voids or credits, so an import that picked the wrong path bills a customer a second time and the fix happens in the admin console, by a person, after the customer has already seen the charge. So the agent never picks. It assembles the order either way, then posts: "Order 41-8823 arrived from the marketplace feed with payment reference ch\_1P2x already settled for 1,284.00 USD. Importing it with Create Order records the settlement. Running the cart pipeline would charge this card again and this connector cannot reverse that. Import as settled?" The operator answers, and the agent proceeds down one branch. What made this safe was not better matching logic. It was that the choice between recording money and taking money belonged to a person. 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 115 actions ### Orders 22 - **List Orders** Reads a page of orders with the full filter, sort and field projection syntax. The workhorse read behind every sweep, and the place to spend an Expand rather than a second call. - **Get Order** Reads one order by id. Expand pulls items, payments, shipments and custom fields in the same call, because nested collections come back empty otherwise. - **Create Order** Writes an order record directly and recalculates nothing. This is the import path for an order that was already priced and paid on a marketplace, a phone call or an EDI feed. - **Update Order** Updates an order's fields. Totals are not recalculated for you, so a flow that adds lines afterwards owns the arithmetic. - **Set Order Status** Moves an order to a status defined on that store. Statuses are per store, so the flow reads them live rather than assuming an id. - **Delete Order** Permanently deletes an order and usually its nested collections with it. A canceled status is the reversible alternative. - **Get Order Items** Reads the line items on one order. - **Get Order Payments** Reads the payment records attached to one order. A console token cannot read encrypted card data, so blank card fields here are expected. - **Get Order Shipments** Reads the shipment records attached to one order, including tracking numbers already written back. - **List Order Items** Lists line items across orders with the standard filter syntax. - **Create Order Item** Adds a line to an existing order. It does not move the order totals, which the flow updates itself. - **Update Order Item** Changes a line on an existing order, for a substitution or a quantity correction. - **Delete Order Item** Removes a line from an order. - **List Order Shipments** Lists shipments across orders, which is how a flow finds orders that left the warehouse but never got tracking. - **Create Order Shipment** Writes a shipment with its tracking number back onto the order. The step that closes the loop after a warehouse or 3PL ships. - **Update Order Shipment** Corrects a shipment record, usually a tracking number that changed carrier or was rekeyed. - **List Order Payments** Lists payment records across orders, for settlement reconciliation against an accounting system. - **Create Order Payment** Records a settlement that happened somewhere else against the order. It records money, it does not take money. - **List Order Addresses** Reads the frozen address copies attached to orders, which is what an order actually shipped to. - **Create Order Address** Creates the order address record an imported order will point at. Create Order needs these ids, not customer address book ids. - **Update Order Address** Corrects an order's frozen address, for a delivery exception caught before dispatch. - **List Order Statuses** Lists the order statuses this store defines. The smallest authenticated read, and the connection test. ### Quotes and Subscriptions 7 - **List Quotes** Lists B2B quotes with the standard filter syntax, which is how a flow finds quotes that have gone quiet. - **Get Quote** Reads one quote with its lines and terms. - **Create Quote** Creates a quote for a buyer, typically from a request captured elsewhere. - **Update Quote** Revises a quote's lines, pricing or expiry as a negotiation moves. - **List Subscriptions** Lists recurring subscriptions, which is how a dunning flow finds the ones about to renew or already failing. - **Get Subscription** Reads one subscription with its schedule and payment state. - **Update Subscription** Changes a subscription's schedule, quantity or state, for a pause, a plan change or a card update. ### Cart and Checkout 13 - **List Carts** Lists carts with the standard filter syntax. A nightly sweep for carts older than a day with no order behind them is the abandoned cart list. - **Get Cart** Reads a cart's contents as stored. Prefer Get Calculated Cart when totals matter. - **Create Cart** Opens a cart. The first step of the pipeline that prices, rates and charges. - **Add Cart Items** Adds lines to a cart. - **Update Cart Items** Changes quantities or options on lines already in the cart. - **Remove Cart Items** Removes lines from a cart. Called with no ids it clears the whole cart, which is the vendor's documented behavior rather than an error. - **Calculate Cart Shipping** Rates the live carriers for the cart. It is also the only source of the composite shipping identifier Set Cart Shipping Method needs, which cannot be assembled by hand. - **Set Cart Shipping Method** Selects one of the rated carrier options using the identifier Calculate Cart Shipping produced. - **Set Cart Shipping Estimation** Sets the destination used to estimate shipping before a full address exists. - **Apply Cart Coupon Code** Applies a coupon to the cart and lets the store evaluate whether it qualifies. - **Get Cart Payment Methods** Lists the payment methods available to this cart. - **Get Calculated Cart** Forces a recalculation of pricing, shipping and discounts and returns the result. The read a person should see before anything charges. - **Place Cart Order** Converts the cart into an order and takes the payment. It is the only operation here that charges a card, and nothing in this connector reverses it. ### Products and Variants 20 - **List Products** Reads a page of products with filtering, sorting and field projection. - **Get Product** Reads one product, optionally filled with every nested collection it has. - **Create Product** Creates a product. The store requires only name, price, primary category and status, whatever the vendor's own specification claims. - **Update Product** Updates a product's fields. The write end of a PIM or supplier feed sync. - **Delete Product** Permanently deletes a product and its nested collections. Hiding the product is the reversible alternative. - **List Product Variants** Lists the variants of a product. - **Create Product Variant** Creates a variant under a product. - **Update Product Variant** Updates a variant's own fields. - **Delete Product Variant** Permanently deletes a variant. - **List Variant Inventory** Lists the inventory items behind a product's variants. - **Create Variant Inventory Item** Creates the inventory item a variant is stocked against. - **Update Variant Inventory** Updates a variant inventory item's own attributes. - **List Product Pricing** Lists the price rows on a product, including tiered and customer type pricing. - **Create Product Price** Adds a price row, which is how tiered and B2B pricing arrives from an outside master. - **Update Product Price** Changes an existing price row. - **List Product Pictures** Lists the images attached to a product. - **Add Product Picture** Attaches an image to a product, usually from the same feed that supplied the copy. - **List Product Reviews** Lists product reviews, which is how a moderation flow finds what is waiting. - **Update Product Review** Updates a review, which is the approve, reject or edit step of moderation. - **List Product Statuses** Lists the product statuses this store defines. ### Catalog Structure 8 - **List Categories** Lists the store's categories. - **Get Category** Reads one category with its settings. - **Get Category Products** Lists the products filed under a category. - **Create Category** Creates a category node. - **Update Category** Updates a category's name, placement or settings. - **Delete Category** Permanently deletes a category and usually what hangs beneath it. - **List Manufacturers** Lists the manufacturers defined on the store. - **Create Manufacturer** Creates a manufacturer record, typically when a supplier feed introduces a brand the store has not carried. ### Inventory 6 - **Get Inventory** Reads the stock position for an item, addressed by product id, variant inventory id, SKU, GTIN or name. A warehouse feed that only knows a barcode does not have to resolve it first. - **Add Inventory** Adds stock relative to the current number. Two receipts landing at once cannot overwrite each other, which is why event driven flows use this rather than a set. - **Remove Inventory** Removes stock relative to the current number, for damage, shrinkage or an outbound the storefront did not create. - **Set Inventory** Writes an absolute stock number. Right for a nightly full count, wrong for anything that races a live storefront order. - **Get Inventory Settings** Reads whether stock comes down when an order is placed or when it ships. Read this before writing a stock sync, because it decides whether your numbers will ever agree with the store's. - **Update Inventory Settings** Changes the store's inventory behavior, including when stock is deducted. ### Customers and Addresses 12 - **List Customers** Reads customers with the standard filter syntax, which is how a flow resolves a buyer before importing an order. - **Get Customer** Reads one customer record. - **Create Customer** Creates a customer. - **Update Customer** Updates a customer, including credit limit and payment terms on a B2B account. - **Delete Customer** Permanently deletes a customer. Marking the account inactive is the reversible alternative. - **Get Customer Addresses** Reads one customer's address book. - **List Addresses** Lists address book entries across customers. Editing one of these does not change an order that already shipped to it. - **Create Address** Adds an entry to a customer's address book. - **Update Address** Updates an address book entry. - **Delete Address** Removes an address book entry. - **List Customer Types** Lists the customer types this store defines, which is what B2B pricing tiers hang off. - **List Customer Payment Methods** Lists a customer's stored payment methods. Card fields come back blank to a console token by the vendor's own design. ### Promotions and Mailing Lists 9 - **List Coupon Codes** Lists coupon codes with their conditions and use counts. - **Create Coupon Code** Issues a coupon code, including the single use codes a recovery campaign hands to one shopper each. - **Update Coupon Code** Changes a coupon's value, conditions or expiry. - **Delete Coupon Code** Deletes a coupon code. Deactivating it is the reversible alternative. - **List Gift Certificates** Lists gift certificates and their balances. - **Create Gift Certificate** Issues a gift certificate, which is a common goodwill response to a service failure. - **List Mailing Lists** Lists the store's mailing lists. - **Get Mailing List Members** Reads the members of a mailing list, which is how an email platform gets its audience. - **List Discount Methods** Lists the discount methods configured on the store. ### Store Configuration 7 - **List Stores** Lists the storefronts on the account. A webhook fires only for its own store, so a multi store merchant checks this before assuming coverage. - **List Warehouses** Lists the warehouses defined on the store. - **List Store Locations** Lists physical store locations, for pickup and local fulfillment routing. - **List Shipping Providers** Lists the configured shipping providers. - **List Payment Methods** Lists the payment methods the store accepts. - **List Regions** Lists the regions the store recognizes, which tax and shipping rules key off. - **List Users** Lists admin users on the store, which is how a flow resolves who to notify. ### Webhook Subscriptions 4 - **List Webhook Subscriptions** Lists the store's webhook subscriptions and the events they carry. - **Create Webhook Subscription** Registers a webhook subscription against one of the fire and forget events. AmeriCommerce signs nothing it sends, so treat a delivery as a notification that something changed and read the record back before acting. - **Update Webhook Subscription** Changes a subscription's event type or callback URL. - **Delete Webhook Subscription** Removes a webhook subscription, which is the clean way to retire a callback URL that has been shared too widely. ### Generic Record Access 7 - **List Records** Lists records for any of the store's roughly seventy resources, which is how a flow reaches blogs, redirects, tax rates, custom fields and the rest of the long tail. - **Get Record** Reads one record from any resource, optionally filled with every nested collection it has. - **Get Records By IDs** Reads many records in a single call. On a store limited to five calls per ten seconds this is the most useful operation in the connector. - **Get Nested Records** Reads a nested collection under a record without a second lookup. - **Create Record** Creates a record on any resource. The store treats a create carrying an identifier as an update, so leave the id out unless that is deliberate. - **Update Record** Updates a record on any resource. - **Delete Record** Permanently deletes a record on any resource. ## Frequently Asked Questions ### What can FlowRunner do with AmeriCommerce (Cart.com)? FlowRunner agents can run List Orders, Get Order, and Create Order in AmeriCommerce (Cart.com), plus 112 more actions. ### Does connecting AmeriCommerce (Cart.com) to FlowRunner require OAuth? No. AmeriCommerce (Cart.com) connects to FlowRunner with an API key, no OAuth flow required. ### Can AmeriCommerce (Cart.com) trigger a FlowRunner workflow automatically? AmeriCommerce (Cart.com) doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at AmeriCommerce (Cart.com)?** This integration exposes AmeriCommerce (Cart.com) to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/americommerce. Site index: https://flowrunner.ai/llms.txt