BigCommerce, ready to run.
The BigCommerce integration runs the cases your support team keeps handling by hand. Floowed reads the order, the customer history and the payment behind it, applies your refund and goodwill rules, and acts on the order.
What it does.
What Floowed reads from BigCommerce
- Orders, products ordered and status
- Customers, and the orders behind them
- Transactions and refunds already issued
- Catalog and inventory, where a rule depends on them
What it writes back
- A refund, where the rules allow one
- Order status set to match the decision
- Staff notes on the order recording what was decided and why
- A coupon or discount, where the decision creates one
Three things BigCommerce decides rather than we do. The decision is written to the staff notes, which your team sees and the shopper does not, and we leave the customer's own comment field alone rather than overwriting what they wrote. Order statuses are a fixed list you can rename but not extend, so the outcome maps onto one of theirs. And a refund needs the original payment settled first and does not put stock back, so returning the item to inventory stays a separate step.
A damaged-item refund, from customer complaint to closed ticket.
- Gather
A customer reports a damaged item in Zendesk. We pull the order, the customer's order history and the transactions from BigCommerce, and the tracking from ShipStation.
- Interpret
We read the photo the customer attached and check it against the product ordered and the delivery record.
- Chase
The photo doesn't show the damage, so we ask the customer for a clearer one and follow up until it arrives.
- Decide
Your refund and goodwill rules run in the deterministic policy engine. A claim above your limit goes to the support lead to decide.
- Act
We issue the refund in BigCommerce, set the order status, add a staff note, record the refund in QuickBooks and close the ticket.
Used in the same case
The connection, in detail.
How it connects.
- 1
Connect BigCommerce
Using a store-level API account; the token is sent as X-Auth-Token. Nothing migrates and nothing is replaced.
- 2
Build your operation
Describe it in Slack, Teams or the Floowed Dashboard. Floowed builds it and asks only what it can’t work out.
- 3
Let it run
Every case runs from request to outcome, the same way each time, with the reasons on record. Anything sensitive waits for a person.
Questions
Does Floowed integrate with BigCommerce?
Yes, across orders, customers, transactions and refunds, using a store API token your admin issues with the scopes it needs.
How does the BigCommerce integration connect?
Your admin creates a store-level API account with the least scopes the case needs and gives us the token. Scopes are per resource, modify or read-only, and the account can be removed from the store at any time.
What can Floowed do with BigCommerce data?
A refund request is a case: what was ordered, what arrived, what this customer has done before, and what your policy says. Floowed gathers and reads it, your refund policy decides, and Floowed acts on the order. A refund goes back through your gateway once the payment has settled, or is marked offline when the money was taken outside BigCommerce.
Does a refund put stock back?
No. BigCommerce's refund API doesn't return items to inventory, so restocking stays a separate step your rules can decide.
Is my BigCommerce data secure?
The token carries only the scopes you grant and can be revoked from your store. Card details stay with your payment gateway.
What does the BigCommerce integration cost?
Nothing extra. Integrations are included, and you pay for the work Floowed does on a case. Start free with $80 of credits, no card and no sales call.
Start with BigCommerce. Add the rest.
Free to try, no card, no sales call. Your first $80 of credits is on us.