Surface by surface
| Surface | What the visitor sees |
|---|---|
| Product page | Replacement text in place of the price; no add-to-cart button. |
| Collection page | The same replacement text on each locked card; the collection still renders. |
| Cart | A locked line item is flagged and cannot proceed to checkout. |
| Direct cart permalink | The item may be added, and checkout is blocked with your message. |
| Draft order invoice | Blocked if the customer is unauthorised, so a leaked invoice link is not a way in. |
| Shop app | Price withheld; the Function blocks the order the same way it does on web. |
| Google / Shopping feed | Price omitted from structured data and the feed when Hide price from Google too is on. |
The blocked-checkout message
At checkout the customer sees the message you wrote, not a system error. The default reads: This order includes items available to approved wholesale accounts. Log in with an approved account, or apply for access. Edit it in Settings → Storefront text, and translate it per language. Nothing in the message mentions Prime Lock; the copy is yours.
What the merchant sees
On Pro, every block is written to the blocked-checkout log with the timestamp, the lock that fired, the product, and whether the visitor was logged in. The log is the evidence that the gate is working: if a competitor was collecting your wholesale prices through cart permalinks, you can see it stop.
Running enforcement without hiding
Settings → Enforcement lets you turn storefront hiding off and keep checkout validation on. Prices stay visible to everyone, which keeps your product pages fully indexable, but only authorised customers can complete an order. Some MAP and distributor agreements are the other way round, so the two layers are configured independently.