Which doc decides a shipping app's plan

The hero promises postcode, weight, and a visual flow. Checkout then shows the zone’s flat rate and nothing else. That is often the plan, not a broken condition. The question in “how to evaluate Shopify shipping rate app docs” is which URL is allowed to decide the plan, and which URL only repeats the hero.

The example is OO - Shipping Rates & Rules, because its docs draw that line in one short article. The listing uses Rates, plural. Some docs say Rate, singular. The install link stays the listing.

Must-haves

An answer without these sentences is a brochure.

• Custom prices through the carrier are in a plan article, not only in a “Carrier-based” chip.

• That article names Advanced or higher, a development store, Plus, or a shop where the carrier is already active. A lower plan name is not an automatic yes. Grow on yearly billing is not a yes either, unless the app docs say so. They do not.

• Hide, rename, and reorder live on a different page, and that page must not be quoted as “needs Advanced” when the docs say the opposite.

• The carrier has to be attached to every zone or market where you expect it. A zone inside the app with no Shopify attachment shows nothing.

• Activity logs have a retention the docs name. “You can see why” without a window is vague.

• The listing shows price, reviews, and whether Built for Shopify is present. Zero reviews stay zero.

• Shopify Help on carrier-calculated shipping is the source for what the merchant’s Shopify plan includes. A failed fetch of that Help page is not a license to invent a fee.

Heavy sources and light ones

The chips run from flat fee and ZIP through geolocation and multi-currency. The hero is narrower: a visual flow or an AI draft, fixed or tiered or per-unit prices, discounts and fees, 40+ conditions, one combined checkout line, hide or rename or reorder, and logs. Quote the hero and the docs. A chip counts only when an article repeats it.

The listing, 6 November 2026

Free. No paid card. Rating 0.0 from 0 reviews. The page says there are no reviews yet. Do not invent stars. No Built for Shopify line in the header above the price. Other apps in this set have the badge. This one does not. So there is no citation of a ten-point Lighthouse drop or a checkout p95. Shopify’s requirements page is for apps that earn the mark. This listing has not.

Language: English. Works with Checkout. Launched 28 October 2026. Developer: Online Origins. Resources include the privacy policy, a FAQ, and a documentation link. On this fetch the docs URL is actually on the listing, which is worth saying because not every app card in the same check exposed one.

Data access includes device data with geolocation and IP, the store owner, customers, products, orders, discounts, Shopify Functions, Online Store, and custom data. Geolocation on the panel fits an app that can use location as a condition. It is not proof that every rate is a GPS reading. The privacy policy is the general page: personal information is not stored outside Shopify, log files last only while an issue is open, no third-party sharing except when the law requires it. No separate DPA on that page.

The page that gates the price

Shopify plan requirements, reread 6 November 2026, last updated in the docs fourteen days earlier. It is short on purpose.

To return custom prices through the OO - Shipping Rate & Rules carrier service, the shop typically needs:

• Advanced Shopify or higher, or

• a development store or a Partner development store, or

• Shopify Plus or a similar enterprise plan.

If the carrier is already active on the shop, the app treats the store as eligible even when the displayed plan name looks lower. That is the only exception on the page. It does not say yearly Grow counts.

Delivery customization, hide, rename, and reorder, works on more plans. You do not need Advanced only for that.

Inside the app, an eligible shop sees the full checklist: zones, carrier attachment, optional delivery rules, test checkout. A blocked shop sees a plan banner and a delivery-focused checklist.

Shopify Help on third-party carrier-calculated shipping is the other primary source for the merchant’s subscription. This run did not get a readable article back from that URL, only a connection check. No Grow fee and no “included on annual billing” line is quoted from Help here. The app docs stay the source for whether this carrier returns a price. Help stays the page you open yourself for the Shopify bill.

The next three URLs, in order

Attaching the carrier is its own article: zones or markets. A flow saved in the app with no attachment explains an empty checkout more often than a wrong postcode.

Delivery customization is a separate canvas. It changes methods already at checkout, from Shopify or from a carrier. The activity log is about carrier rate requests. This article does not claim every hide rule appears in that log.

Test checkout and activity logs, also reread today: confirm the carrier is attached, add a product, open checkout with a matching destination, then Shipping rates, Activity logs. Logs keep seven days of carrier requests: which zones matched, which rates came back, why a path did not apply. One entry shows cart lines, currency, destination, and the per-zone evaluation. Older than seven days is gone. A promise of a permanent archive is false.

The conditions collection covers destination, cart, product, customer, and metafields. The collection page is an index. Do not promote a “Distance-based” chip into a per-kilometre tariff unless an article spells that out. The hero’s citable line is 40+ conditions, from postal code and dimensional weight to products, customer tags, and date.

The note on logs and the checkout test walks the seven days and the test steps. This note is about which URL is allowed to say that.

When profiles are enough

Shipping profiles and a flat rate per zone are enough when each country is one price, or a few weight breaks the admin already holds, and you do not need to hide or rename anything. A carrier app is then an extra plan requirement with no gain. A Basic store that only wants to rename a method does not need Advanced for that rename. That store needs the delivery page, not the carrier. A Basic store that wants its own price per postcode does not get it from this app unless the carrier is already active. The plan article is clearer than the hero.

Reviews

There are none. Every star bucket is zero. Launched 28 October 2026. You do not score continuity from stars. You score it from docs that write down the plan gate and the log window, and from the fact that the app is days old in this measurement. That is a weakness. The functional source is strong where it names the gate. An older app with hundreds of reviews wins the reputation row. This app wins the row “the plan page says Advanced, and the hide page says Advanced is not required for hide,” because both sentences are in the docs on 6 November.

Primary sources

• Listing, 6 November 2026

• Shopify plan requirements

• Activity logs, 7 days

• Attach the carrier

• Delivery customization

• Conditions

• Docs collection

• Privacy policy

• Shopify Help on carrier-calculated shipping, open it yourself. This run could not cite the article text.

Close

The hero may promise the flow. The plan article decides whether checkout shows a custom price. Hide and rename are the lighter requirement. Logs are seven days, not an archive. Zero reviews and no badge belong in the same paragraph. With those sources, the pick for a shop that wants tiers, postcode, and one combined checkout line, and that is on Advanced, Plus, a development store, or an already active carrier, is OO - Shipping Rates & Rules. On Basic, with no active carrier, the docs win by saying no.