If your restaurant runs on PAR POS, Stream imports your menu and business hours from PAR so your delivery platforms follow the setup you already have in PAR.
What Stream imports from PAR
Your menu, including items, modifiers and taxes
Your online-ordering menu (the menu you designate in PAR, see below)
Your business hours
Whether your primary register is online or offline
What you need for each location
PAR issues access one location at a time, so connecting PAR works a little differently from most point-of-sale systems. Have these ready for each location:
An API location token. PAR emails this to your registered address when your location is added to your API account. Each location has its own token. They are not interchangeable.
Your account access token. Issued once for your whole PAR account, and the same for every location on it.
Your PAR location ID. PAR does not currently send this alongside the token and it cannot be looked up automatically, so please have it to hand when you connect. Your PAR onboarding contact can provide it.
Both tokens are permanent. They do not expire, and you will not need to reconnect or refresh them on a schedule.
Your delivery menu
We recommend designating an online-ordering menu in the PAR Admin Portal, under Settings Editor → Menu Items → Menu Categories → Menus. When one is designated, Stream reads that menu rather than your full in-store menu, so you decide exactly what delivery customers see.
If no online-ordering menu is designated, Stream builds a default menu from the item groups set up in PAR. That can include items meant only for the register, such as add-on or adjustment buttons, so review the default menu before going live, or designate a menu to control it precisely.
Your taxes
Stream reads the percentage taxes that apply to each item in PAR and shows them on your delivery menus. Flat-fee taxes, and taxes that apply only to certain order types, are not shown on the menu.
Your business hours
Stream reads the business hours you have configured in PAR, so your delivery availability follows what your PAR setup already says. Because PAR does not notify us when hours change, a change reaches your delivery platforms on the next sync rather than instantly.
If a connection fails
PAR returns the same "unauthorized" response whether a token is wrong, mistyped or missing, and it does not say which of the two tokens was at fault. If a location fails to connect, re-check both tokens.
Going live
PAR requires integrations to complete its validation programme before production access is granted. Your go-live date depends partly on PAR's sign-off, which sits outside Stream's control.