Skip to content

New Integrations/Tokens

Troubleshooting

Unhealthy

Validate the store was actually open. Our Par integration is usually pretty strong, and the store being closed for a few days has resulted in this false positive due to the way that we monitor integration health.
If the Par integration is showing as unhealthy validate the token and URL.
You can validate the token by clicking the Test Token button on the location's integration details.
If the token is valid it will show a flash message like in Figure 1. Based on what we've seen in the success case most of the time that means that Par's API URL has changed, for example from 8 to 21. Make sure that is correct. It may also mean the client has to make changes such as closing out an EOD report, or that their terminals are offline.
Ensure if you're reaching out to Par that it's because we're not actually getting data. Audits and/or events being missing is not sufficient reason to reach out to Par.
If the token is invalid, and not improperly copy pasted, reach out to Par's support at .
Set the subject line to `No orders received for store $STORE_NAME on $DATE`.
In the body of the email include the value from the integration's external_id field in admin, and the url base from admin. cc
Send the above as text, not a screenshot of our internal admin app.

Misc

We're seeing weird line items (inappropriate, car makes and models etc)?
Par employees can and often do enter arbitrary line items for various things. Occasionally it's inappropriate, but occasionally it's things like the car Make and Model to help with drive-thru.

Figure

Figure 1

Screen Shot 2022-06-20 at 10.19.15 AM.png
182.3 kB

Want to print your doc?
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.