Which badge is which?
Four labels turn up in commerce and ERP proposals and they are not tiers of the same thing. Two are issued by Acumatica against published criteria, one is issued by a commerce platform’s app store against its own policies, and one is issued by the vendor to itself.
Read the last column of the table before the others. It is the one your client thinks the badge has already answered.
| Criterion | Who grants it | What gets checked | What it stays silent on |
|---|---|---|---|
| Acumatica Certified Application | Acumatica. Required to reach ADN Level 2, which is required to list in the Marketplace. | A test engineer deploys the customization on a clean instance, runs Acuminator static analysis and functionality verification, and checks naming conventions, TLS 1.2, credential encryption, API usage limits, documentation and performance impact. | Whether the application does the job your client needs. Certification is a platform-hygiene review, not a fitness assessment. |
| Fulfilled by Acumatica | Acumatica, to a hand-selected subset of certified vendors. | Ten or more satisfied mutual customers, an Always Current commitment, and the commercial arrangement that puts the app on Acumatica’s price list. | Anything technical beyond certification. Acumatica does not publish an extra code review for the programme. |
| Listed in the Shopify or BigCommerce app store | The commerce platform, against its own app review and policy requirements. | Technical and policy compliance for the platform: authentication, API behaviour, billing, data handling, listing accuracy. | ERP behaviour entirely. No commerce platform reviews whether an app maps your client’s Acumatica price classes correctly. |
| "Validated", "certified integration", "works with"This is the label most likely to appear in a proposal your client is comparing against yours. | Usually the vendor, about itself. | Nothing standardised. Sometimes it means a real joint test, sometimes it means a logo on a slide. | Everything. Ask what the word means in this specific case and who else was in the room when it was granted. |
Checked against: Acumatica community 34096: ADN Level 2 is the minimum to list, and technical certification (ACA) is one of its requirements. Answers dated January and February 2026, Acumatica ISV Software Certification Guidelines, 2020 R1 (PDF), Acumatica blog, "Fulfilled by Acumatica", published 14 March 2023, read 20 August 2026
What does certification actually check?
Acumatica’s ISV Software Certification Guidelines are public, and reading them once is worth more to a partner than any number of vendor conversations. The checks fall into categories a developer would recognise: framework and naming conventions, database design, static analysis with Acuminator, security including TLS 1.2 and encrypted credentials, PCI DSS where payments are involved, web services API guidelines with a limit on records per call, user interface consistency, installation and upgrade documentation, and a requirement that the solution does not degrade Acumatica ERP performance.
Acumatica’s own guidance post from 7 May 2022 describes certification as a process where technical, functional, documentation and other requirements are checked against application standards. So there is functional testing in it. What is being tested is that the app works as the vendor documented it, on a clean instance, without breaking the platform.
That is a meaningful bar and it screens out real problems. It is a different question from whether the app models contract pricing the way your client’s contracts are actually written, and certification was never designed to answer that question.
Checked against: Acumatica blog, "ISV Solution Certification Guidance", published 7 May 2022, read 20 August 2026
What none of the badges tell you about the vendor’s pricing model
Here is the plain answer the badges never give. A connector can be certified, hand-selected, on Acumatica’s price list, and still be the wrong commercial fit for your client, because certification tests the software and says nothing about how the vendor charges.
Three pricing metrics cause most of the trouble. Per-order pricing looks cheap on a client doing 20 orders a day and stops looking cheap the moment the storefront works, which is the outcome you were hired to produce. Per-item or per-SKU-synchronized pricing punishes exactly the distributors who most need a connector, because a 60,000 item master is normal in that segment. Per-storefront or per-store pricing collides with any client who has a second brand, a second region, or a dealer site, and multi-store is one of the requirements that most often turns up late.
There is a second and quieter version of the same problem. The vendor’s data model may not survive the client’s price book even where the licence cost is fine. If your client prices by customer and item with effective dates, and the connector models pricing as customer groups mapped to platform price lists, the mismatch is architectural. It will not be solved by buying a larger tier.
So test the price book against the product, not against the badge. Take 20 real customer and item combinations out of the ERP, including the ugliest ones with dates and units of measure, and ask the vendor to show them working. A vendor who can do that in a demo has told you more than any badge could.
Checked against: Acumatica community 17608: only Default Price is supported for the Shopify connector, so the effective sales price does not publish, Shopify Help Centre: on Basic, Grow and Advanced plans you can assign up to three active catalogs across all B2B markets; unlimited catalogs and direct assignment to companies and locations are Plus. Read 20 August 2026
How do you do 30 minutes of real diligence on a listing?
Thirty minutes, once per vendor, reusable across every deal you take that vendor into. Nothing here needs the vendor’s cooperation except the reference request, and a vendor who resists that request has answered a different question for you.
Do this before the connector appears in a proposal, not after. Once a vendor name is in a document a client has read, changing it costs you credibility that the diligence would have protected.
Search the vendor’s name in the Acumatica community and read the last two years of threads. Unresolved threads with no vendor reply are the signal, not the count of threads.
Check which ERP release the listing states support for today, and ask what happens on the next major release.
Ask for a reference on the same ERP release, the same commerce platform, and the same pricing complexity. Accept two out of three only if the third is pricing.
Model the vendor’s pricing metric at three times the client’s current order and item volume, and put the resulting number in your internal file.
Ask where support sits, what the hours are, and what the response commitment is for an outage that stops orders.
Ask what happens to the client’s data if the client cancels: what is exported, in what format, and how long the vendor retains it.
Which badge should actually change your recommendation?
Fulfilled by Acumatica should change your procurement plan. One price list, one renewal, one bundling conversation, and an update cadence you can point at when the client’s IT team asks about upgrade risk. Those are real advantages and they belong in your proposal.
No badge should change your architecture. If the client has dated contract prices per customer and item, the badge on a connector does not change where price has to be calculated, and a certified connector that copies stored fields will publish the same list price as an uncertified one.
The signal that should change your recommendation is the reference call. A vendor with a customer who looks like your client, on the release your client is on, running the pricing model your client runs, has given you the only evidence in this whole conversation that is about your client. Everything else is about the vendor.
Common questions
- Is "Acumatica Certified" the same as "Fulfilled by Acumatica"?
- No. Acumatica Certified Application is the technical certification every Marketplace listing needs, since listing requires ADN Level 2 and certification is one of the Level 2 requirements. Fulfilled by Acumatica is a hand-selected commercial tier on top of certification, requiring 10 or more mutual customers and an Always Current commitment, with the app sold on Acumatica’s own price list. Vendors sometimes use the two phrases interchangeably in marketing, and they are not interchangeable.
- Can an uncertified application run on Acumatica?
- Yes. Certification is about publishing to the Marketplace and reaching ADN Level 2, not about whether code can be deployed. Customizations built by a VAR for one client, and private integrations built against Acumatica’s web services, are not certified and do not need to be. That also means the absence of a badge on a bespoke integration tells you nothing, and the presence of one on a Marketplace app tells you less than clients assume.
- Does certification expire?
- It has to be maintained. Acumatica’s community answer on Marketplace listing describes an ongoing Always Current commitment requiring re-certification within 90 days of a major release as part of ADN Level 2. The practical question for a partner is not whether the badge exists but which release the application is certified against on the day you are proposing it, which is worth asking in writing.
- What does "validated" mean when a commerce vendor uses it?
- Usually nothing standardised, and that is not always dishonest. Sometimes it records a genuine joint engineering test with a named partner, sometimes it records a reseller agreement, and sometimes it records a logo exchange. Ask three questions: who validated it, against which version, and what document came out of it. If there is no document, treat the word as marketing and move on without making a fuss about it.
- What is the single best question to ask instead of checking badges?
- Ask the vendor to show you 20 of your client’s own customer and item price combinations working in their product, including the ones with effective dates and non-base units of measure. It takes the conversation out of capability claims and into your client’s actual data, it is answerable in a demo, and it tells you more about fit than every badge in the category put together.
Last updated 2026-08-20. Facts on this page last checked against source 2026-08-20.