An extension can compile and appear in an admin list while remaining invisible to shoppers. Placement, saved configuration, publish state, runtime match, and store plan sit between code and the page.
Check the five gates
- Implementation.
- Access and scopes.
- Editor placement.
- Published configuration.
- Runtime match and successful request.
Start with the editor
Product Page and Cart Drawer paths need a Theme App Block or App Embed. Checkout, Thank You, and Order Status paths need their corresponding editor placement.
Use a real test order
Test one known trigger, one available variant, and one expected discount. A screenshot of the admin page alone cannot prove runtime behavior.
Write the result down
Record the store plan, extension target, configuration ID, test order, timestamp, discount result, and order event.