Switching to Quay from another credit app

Why running both is safe

The two apps do not fight over your data. Both read the same Shopify companies and the same orders; neither owns them. What could collide is enforcement — two apps both trying to stop the same checkout — and that cannot happen while Quay has no policy assigned, because a company without a policy is a company Quay leaves alone.

So the first week costs you nothing and risks nothing. You get a second opinion on your own accounts receivable: who is overdue, by how long, and which companies are close to their limit. If the numbers do not match what your current app tells you, that is worth knowing before you commit either way.

Bringing your credit limits over

Export the limits from your current app and send us the file. We will read it and load it for you — there is no self-serve importer, and we would rather be honest about that than point you at one that half works.

Fair question at this point: who is holding that file, and what happens to your numbers afterwards. That is answered on the security page — what Quay reads, what it stores, and what is deleted when you leave.

Doing it by hand has turned out to be the better deal anyway, because export files are never clean. In the migrations we have run so far we found limits still sitting on cancelled accounts, the same company listed twice with different numbers, and rows in a currency that did not match the store. We come back with a list of what looks wrong and you decide, before anything is written to your store.

The one thing that catches people out

If your current app shows your buyers anything — a page in their account where they check their own balance, credit or unpaid invoices — that screen goes away the moment you uninstall it. Buyers who used it will notice, and they will ask your team instead.

Quay has its own version, a Finance and payments page inside Shopify's own customer accounts, showing the company's next due date, amount due, total outstanding and, if you want, its credit limit and how much is left. It is not on by default: you add it once in the customer account editor.

Do that before you uninstall the old app, not after. It takes a few minutes and it is the difference between your buyers never noticing the switch and your team fielding a week of questions.

A sensible order to do this in

• Install Quay. Assign no policies. Look at the AR numbers for a few days.
• Send us your export; we check it and load your limits.
• Turn on Quay's buyer page in the customer account editor.
• Assign a policy to a handful of companies and watch what happens at checkout.
• Widen it to the rest.
• Only then uninstall the old app.

Still weighing whether to move at all? The capability-by-capability comparison with native Shopify B2B is the more useful question than app versus app: if native already covers you, neither of us is worth paying for.

Where credit rules apply, and where they do not

This is not a Quay setting. Shopify decides which parts of your store run checkout rules at all, it publishes the list, and it is the same list for every credit app on the App Store. Worth reading before you move, because it is the part nobody tells you until something slips through.

Buyers checking out themselves: covered. Online store, your own storefront, and the invoice or payment link you send from a draft order. This is where most B2B credit actually leaks, and it is the case Quay can stop outright.

Your team creating orders in the admin: rules run, staff can override. Shopify shows your team the block when they create a draft order and again when they complete it. What it does not offer is a way to make that binding — a staff member can choose "Ignore and create order", and no permission separates "may create draft orders" from "may override validation". So Quay makes the override visible instead of pretending it cannot happen: a Telegram message lands in seconds with the order, company, amount, the reason it should have been stopped, and who placed it.

Shopify POS: depends on how your till records the sale. Shopify lists POS as unsupported, so a native POS sale — ring it up, take payment at the counter — runs no credit rules at all, from any app. But some B2B POS apps put the sale through a draft order instead, and draft orders are supported, so there the rules do run, with the staff override above still available. Which of the two you have depends on your POS app, so test it on your own till rather than taking anyone's word for it.

Orders pushed in by an integration: not covered. If an ERP or a script creates orders through Shopify's order API, Shopify runs no checkout rules on them. Quay still counts those orders against the company's balance, so your numbers stay right, but nothing stops them being created.

Frequently asked questions

Something here not covered? Write to [email protected] and describe your current setup — we would rather tell you Quay is a bad fit than have you find out after you switch.