How do you judge Shopify B2B app support and developer continuity?

Finance wants a name when a wholesale price is wrong for one company and the VAT reverse charge did not fire. A Built for Shopify badge does not name that person. On 10 November 2026 I opened the live listing for OO ‑ B2B & Wholesale, the privacy policy the apps point at, and the support line plus the data-access block on that listing. I read the three review cards on the screen. I did not find a status page or a response-time table, because those two URLs do not publish one.

Shopify’s own B2B companies are a different question, covered in the 4 November note. Theme blocks, the cart drawer snippet, and what uninstall removes are the 5 November note. This note is the vendor test in between: what you can verify on a Monday morning before you hang VAT logic on one developer, and what the listing refuses to promise. Re-open it if the badge drops, if review replies go quiet, if the privacy page gains a processing agreement or changes the contact, or if Starter or Growth changes price.

A vendor checklist you can fail

The docs collection is still the URL the app publishes. Articles there are signed by Floris de Vries and carry a last-updated line. That date is when you re-read, not a service level.

The three cards, and the review you cannot see

• 6 October 2026, Sensorkranenwinkel.nl, about two years on the app. VAT reverse charge works, and support answers quickly. The review is in Dutch.

• 11 June 2026, POPlab Sounds, Germany, five months. They could rename the note field so it lands in their bookkeeping.

• 21 April 2026, Rohleder AT, Austria. The card mentions a FAQ, a chatbot that actually helped, translations, and pricing the reviewer called fair. The card’s “using the app” line was about two hours.

All three are five stars. The histogram still counts one four-star review, and its text was not on this screen. For a continuity decision that missing paragraph matters more than the 5.0 average. Open the full review list before you write “no complaints” into a proposal. Counts move. Check the listing again before you paste a number into a slide.

The chatbot and the FAQ live in Rohleder’s sentence. I did not open a docs page that specifies that bot, its hours, or its limits. Quote it as a review, not as a support product.

The listing’s support section is one sentence. No WhatsApp, no ticket portal, no “reply within a day”. The plan cards describe features. They do not describe a service window.

The privacy page is the published contact path

The privacy policy covers Online Origins apps as a group. It says personal information stays in Shopify, log files exist to chase a technical issue and are deleted after, and data is not shared with third parties except when the law requires it. Support may send a collaboration request and may email you about installation or a fault. The contact block is info@onlineorigins.nl, the same ’s-Hertogenbosch address, phone 073 234 0612.

There is no processing agreement on that page. If a DPA is a knockout before wholesale customers enter the app, the item stays open. The page also skips a retention number of days. Mail is kept “no longer than necessary”. Logs last for the incident.

The same address appears on the developer block of the listing. That match is the continuity signal you can actually check. A second brand name, or a support inbox that no longer matches, would change the advice.

Exit is a Shopify-record question

This morning’s data-access block:

• customer name and email, plus device data

• store owner name, email, phone, and address

• edit customers, products and inventory, draft orders and 60 days of order history, discount codes, and companies

• view theme

• locales, locations, Shopify Markets

Script tags were not in the block. Theme was. That fits an install through an app embed and theme blocks, which the 5 November note already walks through. A line you paste into `cart-drawer.liquid` stays when the app leaves. That risk is separate from “the developer disappears”.

Companies and customers are Shopify records. The listing says the app may edit them: an approved registration creates or links a customer and can create a company. The listing does not say uninstall deletes those companies. The privacy page does not say the app keeps a copy outside Shopify. An exit plan, until you test it, is: company and customer records remain in the admin, the app’s price rules do not. Development stores have no caps on the Free card. That is a listing sentence from today, not a data-export promise. Prove the exit on a development store before you write it into a runbook.

Price sits with the vendor, so read the cards

Prices on 10 November 2026 match the 9 November check:

Rohleder’s “fair” is an opinion from April 2026, not a second price source. If Starter or Growth changes amount, read continuity again. A vendor who doubles the card quietly is a different risk from a vendor who answers a VAT question the same week.

Works with: Checkout, Shopify Flow, Shopify Admin. Listing language: English. The Dutch review shows that a Dutch merchant got an answer. It does not publish a language SLA. Do not treat the hero as a promise that support is staffed in every storefront language.

When you skip the vendor question

Skip the app when Shopify’s own companies and catalogs already cover the price, the customer, and checkout. Continuity then belongs to Shopify. The 4 November note draws that line. This note does not restate catalog caps, because I did not re-open that Help page this morning.

Skip the app when a published DPA or a contractual response time is a knockout. Those documents are not on the listing or the privacy page as of 10 November 2026. A kind review is not a substitute.

Primary sources

• OO ‑ B2B & Wholesale on the App Store

• App privacy policy

• B2B and wholesale docs

On this site

Theme placement and uninstall are the technical note. Which URL may carry a claim is the source note. The bill as volume grows is the pricing note. Registration and approval are the 9 November checklist. Companies versus this app: the 4 November note. Shopify apps as a service: apps and integrations.

What holds this morning

Four things are checkable: the same developer on the listing and the privacy page, a launch date of 9 February 2024, a Built for Shopify badge, and recent reviews that mention a human reply. Four things are not a yes: a response time, a DPA, the text of the one four-star review, and the exact uninstall behaviour for companies.

Install from this listing, not from a second wholesale app: OO ‑ B2B & Wholesale. Drop the conclusion if the badge goes, if the privacy page publishes a processing agreement or changes the contact, or if the plan cards change amount.