Troubleshooting & Support
Diagnosing with debug mode
A developer triage walkthrough using the browser console and debug mode.
Diagnosing with debug mode
🛠 Dev
A repeatable triage for when a custom feature misbehaves.
Confirm which API the store is using
In the browser console on the affected page:
window.theme.api.base // production or staging URL?
window.theme.api.debug // true means debug mode is onIf this is the live store and debug is true, that's likely the problem — see
Debug mode.
Check authentication
window.theme.sessionManagerA failing token request (/v1/auth) breaks every downstream call. Look for 401/403s in the
Network tab.
Inspect the relevant module state
window.theme.vehicleDetails // selected vehicle, compatible parts
window.theme.postcodeEntry // current postcode / regionConfirm the state matches what the customer reports.
Watch the network calls
In the Network tab, reproduce the action and watch the /v1/... request:
| Endpoint | Feature |
|---|---|
/v1/vehicle/... | Vehicle lookup / compatibility |
/v1/postcode/... | Delivery zone |
/v1/schedule, /v1/schedule/reserve | Installation booking |
/v1/places | Address autocomplete |
A non-200 response, CORS error, or timeout points to an API problem → escalate.
Check the console for theme errors
A JavaScript error in a module (e.g. analytics.js, installation.js) can stop a flow partway.
Note the file and line and the exact message.
Deciding theme vs API vs data
| Symptom | Likely owner |
|---|---|
| JS error in a theme file; UI broken | Theme (Conversion Kings) |
/v1/... returns errors or times out | Backend API (Conversion Kings, while on retainer) |
| API responds fine but a battery/vehicle/mapping is missing | Fitment data (API-side data) |
| Checkout/payment failure | Shopify platform |
See Escalation & contacts to route it.