What does the Acumatica Shopify connector actually send as a price?
The Acumatica Commerce Connector moves price through named entities, and knowing which entity you have switched on is most of the answer. The Base Sales Price entity carries the stock item’s Default Price. The Price List entity carries Acumatica price lists across to the storefront, and it does not fire on every change: you prepare and process it, manually or on an automation schedule.
The clearest statement of that architecture in Acumatica’s own community is on the BigCommerce side, where a user asked how to get Sales Price Worksheet prices onto the store. The answer was that the Customer Price Class entity “will update groups of customers in BigCommerce store (Customers>Customer Groups), but not the prices”, and that to move prices you “Prepare and Process Price List entity manually or with an automation schedule”, usually overnight. That question was asked on Acumatica 2021 R2. The Shopify side is built the same way, and the Shopify Price List entity is real enough to have its own well-known failure message, “Sync ID is not found for the record”, which fires when any stock item on the list has not already synced.
So the connector is not priceless. It prices at the level of the item and the level of the list. What it does not do is ask Acumatica what this customer would pay for this item today.
Checked against: Acumatica for Shopify Connector product page, Community 11823: syncing sales prices from worksheets to BigCommerce, Community 22606: “Sync ID is not found for the record” on Shopify price list sync
What does Acumatica claim, and what does Acumatica’s own community say?
Both of these were read on 20 August 2026. The vendor page is not lying. It is describing the price-list path and calling the result customer-specific pricing, which is fair as far as it goes. The problem is that an Acumatica user reading that sentence reasonably assumes it means the price Acumatica itself would put on the sales order, and that is the one thing it does not mean.
The community answer came from a Captain II contributor in the Retail and Commerce forum, responding to a poster who had already narrowed the question to the SalesPrice field on the ARSalesPrice table. There was no qualifier and no workaround offered.
| Criterion | Acumatica’s Shopify connector page | Acumatica community |
|---|---|---|
| Customer-specific price | “B2B Customer Specific Pricing: Ensure your customers see their appropriate pricing in Shopify.” | “No. Only Default Price is supported.” Answering whether the current effective sales price can sync instead of the Default Price. |
| Sales Price Worksheets | Not mentioned on the page. | A second user in the thread asks whether that makes Sales Price Worksheets “not usable for anyone that uses Shopify”. Nobody in the thread contradicted him. |
| Volume price breaksThis row is where we would stop and test rather than believe either side. | “Configure and synchronize company-specific volume price break rules, discounts, or promotions from Acumatica with Shopify.” | Not addressed in this thread. We have not verified it either way, so treat it as untested until you have watched a break quantity land in your own store. |
| Price lists for Shopify B2B | “Manage product visibility and pricing by customer type or location.” | The Price List entity exists and does sync. It fails for the whole list when a single stock item on it is inactive or not yet synced to Shopify. |
Checked against: Community 17608: sync current effective sales price to Shopify, Acumatica for Shopify Connector product page, Community 22606: price list sync failure
Why do Sales Price Worksheets make this worse than it sounds?
A Sales Price Worksheet is how an Acumatica user puts a batch of negotiated prices live on a date. You build the worksheet, you release it, and the prices land in the ARSalesPrice table with effective and expiration dates, keyed to a customer or to a A price class is a label on a customer account that decides which set of prices they see. Acumatica and most ERPs use price classes so a seller can maintain one price list for a whole tier of customers instead of one per account.. That table is what Acumatica reads when your inside sales team keys an order. It is, for most distributors, the actual home of Contract pricing is a price that applies to one customer or one group of customers rather than to everyone. In B2B it is normal for the same product to have a different price for every account on the book..
If the storefront reads Default Price and the order desk reads ARSalesPrice, the two channels quote different numbers for the same item on the same day. Nothing errors. The item syncs, the order syncs, the price is simply wrong, and you find out when a customer who has been buying at a negotiated price for four years sees list price on your new website and phones his rep about it.
That is also why this cannot be treated as a launch-week snag. Every worksheet you release afterwards silently widens the gap between the two channels.
Checked against: Community 17608: “Only Default Price is supported”
What are the four ways teams work around it, and what does each cost?
These are the four we see. Nobody gets all of what a Sales Price Worksheet gives them, so the real decision is which property of your pricing you are willing to give up: the number of tiers, the freshness, the effective dating, or the maintenance cost.
| Criterion | How it works | What it costs you |
|---|---|---|
| 1. Price the online catalogue at Default Price | Sell a subset of the catalogue online at one price for everyone, and keep negotiated accounts on the phone or on EDI. | You have not solved contract pricing, you have scoped it out. Honest, cheap, and the right call more often than vendors admit. It fails the moment a contract customer discovers the site. |
| 2. Model prices as Acumatica price lists into Shopify B2B catalogues | Restructure negotiated prices as price lists, switch on the Price List entity, and schedule Prepare and Process overnight. | Shopify caps active B2B catalogues at three on Basic, Grow and Advanced, so more than three tiers means Shopify Plus. Prices are as fresh as last night’s schedule, not as fresh as the ERP. One unsynced item fails the whole list. |
| 3. Call Acumatica for the price at runtime | The storefront asks Acumatica for this customer’s price when the product page or the cart renders, through middleware or a custom app. | This is the general mechanism rather than a connector feature, so budget it as development. You take an ERP dependency on your most performance-sensitive pages, and you need a defined answer for what the page shows when Acumatica is mid-upgrade. |
| 4. Customize the connector to read ARSalesPrice | Extend the Commerce Connector graph so the price entity resolves the effective sales price rather than the Default Price. | You own a customization against a connector Acumatica revises every release. The 25R1 template sync validation change, which started rejecting attributes with duplicate descriptions, is exactly the kind of release-note-free change that breaks this class of customization. |
Checked against: Shopify B2B limitations, LiquidLab (catalogue cap by plan), Community 30860: 25R1 template sync validation change
When is this not your problem?
Four situations where the Default Price limit genuinely does not matter, and you should stop reading and go and solve something else.
The one we cannot call for you is volume price breaks. Acumatica’s page says company-specific break rules synchronize; the thread we cite does not test that, and we have not tested it ourselves. If break quantities are how your pricing works, that is the first thing to prove in a sandbox rather than the last.
Your online catalogue is a subset sold at list, and the negotiated accounts stay on EDI or on the phone.
Your customer discounts are percentages off list held on the customer record rather than absolute prices, in which case a Shopify B2B catalogue can express them as a percentage adjustment and no worksheet is involved.
You have three or fewer price tiers and they change a few times a year, so a nightly Prepare and Process schedule is fresh enough and you never hit the catalogue cap.
You are already committed to Middleware is a layer of software that sits between the ERP and the storefront, translating and enforcing rules that neither system holds on its own. It can be a hosted integration platform or a custom service. for other reasons, in which case the price question folds into a decision you have made anyway.
How do you check this in your own tenant in twenty minutes?
Do this before you sign anything, and do it yourself rather than asking for a demo. A demo tenant rarely has a released Sales Price Worksheet in it.
Pick a stock item that one of your top ten accounts buys at a negotiated price. Note the Default Price on the item’s Price/Cost tab.
Open Sales Prices in Acumatica and note the effective price for that customer today. If the two numbers are the same, pick a different item, because this one will not tell you anything.
Look at the same product in Shopify, signed in as that company if you are on Shopify B2B. Whichever number you see is the answer for your tenant, on your release.
On the store record, check whether the Price List entity is enabled and whether Prepare and Process are on an automation schedule. If they are not, price changes are not reaching the store at all.
Ask your VAR which entity carries the price for those ten accounts. “The connector handles pricing” is not an answer to that question, and a good VAR will not give it to you.
Checked against: Community 11823: Prepare and Process on a nightly schedule
The wider picture
This page answers one narrow question. Acro Commerce covers the strategy around it.
Common questions
- Does the Acumatica BigCommerce connector have the same limitation?
- The shape is the same. In Acumatica community thread 11823, asked on 2021 R2, the answer was that the Customer Price Class entity updates customer groups in BigCommerce but not prices, and that prices move only when you prepare and process the Price List entity, normally on an overnight automation schedule. So on BigCommerce as on Shopify, the connector syncs lists and defaults rather than the effective price Acumatica would calculate for an order.
- Can Shopify B2B catalogues replace Sales Price Worksheets?
- For a seller with a small number of price tiers, yes, and this is the workaround most teams land on. Two limits decide it. Shopify caps active pricing catalogues at three on Basic, Grow and Advanced plans, so more tiers than that means Shopify Plus, and catalogue prices refresh on your Prepare and Process schedule rather than the moment the ERP changes. Effective dating has to be expressed as a scheduled catalogue change instead of a worksheet.
- Which Acumatica release does the “Only Default Price is supported” answer apply to?
- The thread does not state a release, which is a real weakness in the evidence. The related BigCommerce thread that describes the Price List entity behaviour was asked on Acumatica 2021 R2 Build 21.216.0034. Acumatica has shipped 2026 R1 since, and its retail and commerce notes for that release cover marketplace tax and BigCommerce B2B import rather than price entity behaviour. Re-check it against your own release before you rely on it either way.
- Is Acumatica’s marketing page wrong?
- No, and it is worth being precise about that. The page describes managing pricing by customer type or location and synchronizing company-specific price rules, which the Price List entity genuinely does. What it does not say, and what an Acumatica user will assume, is that the effective sales price from a released Sales Price Worksheet is out of scope. The gap is between a fair summary and a reasonable reading of it.
- What breaks first if we launch anyway?
- Trust in the channel, and it goes in a specific order. A contract customer sees list price, phones his rep, and the rep fixes it manually in Acumatica. After that happens twice the rep tells his other accounts to keep phoning him. The portal then looks like it has low adoption, which gets diagnosed as a user experience problem, and the pricing cause never surfaces.
Last updated 2026-08-20. Facts on this page last checked against source 2026-08-20.