Hi Frank21x,
My recommendation would be to create a separate menu for pick orders and use the menu specific pricing structure. We have higher pricing for our Third-Party Menu items. We created a separate menu for those items, which differs from our dine-in and online ordering menus. This allows us to apply a higher pricing structure (e.g., $1 more for entrees and $0.50 more for beverages). We do a combination of location specific and menu specific pricing but that's to achieve tiered pricing we set up internally as our menu prices differ by state and region. If you make price changes frequently, it's important to update both menus accordingly, which can be a bit time consuming. Personally, I prefer to schedule price updates in advance, based on the dates provided by our menu team for the next price revision.
I am not entirely sure if you can achieve different pricing using revenue centers, but I'll include any articles that I find at the bottom of this message. 🙂
Example:
As shown in the pictures below, Tier 2 Pricing- Illinois (location group) has a base price of $16 on our limited time offerings menu for orders placed for dining in or online ordering. For third-party orders, the price is $17.
Price Editor View:
To create menu-specific prices for a menu item
In the Pricing Strategy section of the menu item's details page, select Menu Specific Price.
In the Base Price field, enter a base price for the menu item. This price is used if a menu-specific price for the item cannot be calculated. For example, if you added the menu item to a newly created menu but neglected to update the menu item with a menu-specific price for the new menu.
In the Menu Prices grid, enter the price to be used for the menu item when it is ordered from each menu.
Save your changes.
If you are done editing prices for your menus, publish your changes.
Articles:
Menu-specific price - - Platform guide
Create and Assign Revenue Centers
