Skip to main content

How to Integrate Givex POS

How to integrate your Givex POS with WISK

Nick Neale avatar
Written by Nick Neale
Updated over a week ago

Article Contents

Introduction

To integrate your Givex POS system with WISK:

  1. Contact your Givex representative and request that you want to integrate with WISK

  2. The Givex team will process your request. This typically involves signing an agreement and paying any fees to Givex (if applicable)

  3. The Givex implementation specialist will then set things up and send the required credentials to WISK (These can also be forwarded to [email protected]). This includes the restaurant/location ID

  4. The WISK team adds these credentials to your WISK account/venue and the integration is complete

  5. Your menu items and sales data import into your WISK account / venue

Customizing your Sales Data / POS Items

After the integration is complete, you can customize how your sales data / POS Items appear in WISK. This is essential if you make extensive use of modifiers.

Important: We recommend after connecting your POS to see how the POS Items appear in your account. If you need to customize them further, it's best to do that before you proceed with mapping POS Items.

To customize your sales data:

  1. On the WISK Web Portal, hover your cursor over your username on the bottom left, and click “Venue Settings” on the menu that appears

  2. Scroll down to the "POS Integrations" section and click the “Edit” button beside your Givex integration

    An arrow points to the "Edit" button

  3. The following customization checkboxes are available:

    There are different checkboxes you can toggle on to customize how the sales are imported

    • Include all POS Items even if not sold - By default, WISK only pulls items with sales. If you create a new item in your POS, it won’t appear as a POS Item in your account until it is sold. If you check this box, it will appear as a POS Item before it is sold, and can be mapped.

    • Include Modifiers - If you use modifiers that increase the cost of a menu item, you’ll want to check this box. For example, you have a “Jameson” button in Toast, and then a “1oz” and “2oz” modifier option. Checking this option creates a new POS Item for each modifier at a different price. You can then add the recipe to each POS Item. Otherwise, it will all appear under one “Jameson” POS Item, and you won’t be able to map it correctly

    • Import Modifiers as Separate POS Items - When you select this option, your menu item modifiers appear as separate POS Items. This applies to both modifiers that include an up-charge, and modifiers with a price of 0.

      For example, if you sell an item called "Tito's Vodka Single" and you use modifiers to track the mix it's sold with, it will appear differently depending on whether this box is checked. Lets say we sell it with Orange Juice:

      • Checked - There will be a separate POS Item for "Tito's Vodka Single", and for "Orange Juice". Orange Juice could be used as a modifier in multiple items, and it will only appear as one POS Item.

      • Unchecked - There will be a combined POS Item of "Tito's Vodka Single - Orange Juice"

    • Include text modifiers - Text modifiers are primarily notes that don't affect the ingredients or cost of the item. Examples include "over easy", "medium rare", on "on the rocks" etc. In most cases you won't want this toggled on

    • Include modifiers with price of 0 - If toggled on, modifiers that don't affect the price are imported into your WISK account attached to POS Items. For example, you may have a Pad Thai menu item with a choice of protein (chicken, beef, tofu, etc). If it isn't toggled on, you'll see just see "Pad Thai", but if toggled on there is a POS item for each option that you can map accordingly.

      Other examples include the type of mix used in a drink (orange juice, ginger ale, etc) or the choice of side with an entree (fries, soup, salad). This has the potential to create a large number of POS Items, but can provide greater accuracy with your recipe mapping / costing.

    • Create Separate POS Items by Department - When checked, this creates separate POS Items for each department / revenue center a menu item is sold in. For example, if you sell a Cheeseburger in store, but also on a third-party ordering app (Uber Eats etc.) you would have a POS item called "Cheeseburger - In Store" and "Cheeseburger - Uber Eats". This is helpful if you sell items at different price points depending on the department. This will create more POS Items but allows for more accurate costing.

      When unchecked, sales for menu items appear under a single POS Item. If the price fluctuates depending on the department it was sold in, the menu price in WISK will be whatever the menu item last sold at.

      For more info, see "Creating Separate POS Items by Department"

  4. After making your selections, click "Save". You'll be prompted to reimport your sales data so the changes can apply to sales that have been imported with the old settings.

Creating Separate POS Items by Department

This section provides a more detailed walkthrough of the "Create Separate POS Items by Department" POS Item customization option.

When this option is unchecked, sales for menu items appear under a single POS Item. If the price fluctuates depending on the department it was sold in, the menu price in WISK will be whatever the menu item last sold at.

For example if we sell a "Cheeseburger" for $9.49 normally, but then charge $11.49 when it is sold via a third-party ordering app these sales are grouped together.

In the example below we see the Cheeseburger item with 50 sold in the period for a total of $534.50. It uses those values to calculate an average price of $10.69.

When you click the "Details" button it shows each individual sale at different price points.

When mapping the POS Item, the menu price may show as $9.49 or $11.49 depending on which was sold last. This will cause the cost percentage of the item to fluctuate.


If the "Include departments" box is checked, separate POS Items are created for each department / revenue center a menu item is sold in.

Instead of a single POS Item for Cheeseburger, we now have one for each department it was sold in. Each POS Item has its own menu price.

This adds more POS Items to map, but you can map one and copy the ingredients to the others. You will then get an accurate cost percentage for each price point.

To learn more, see:

Importing Sales From Specific Departments

When the integration is set up, you can choose to import sales from specific departments.

Note: Sales from all departments are imported by default and in most cases you won't need to make any changes to this. When no boxes are checked, sales from all departments are imported.


However, if you have separate venues per revenue center / department in WISK, you'll want to filter the sales accordingly.

If you check the box beside any of the departments, it only imports sales for those selected departments moving forward. After making your changes and clicking "Save" you'll be prompted to re-import your sales data from a specific date. This removes sales from the unchecked departments.

Let's say for example you have 3 restaurants in a complex on a single Givex location ID. You want to see the sales and variance in each restaurant, so you have them as 3 separate accounts in WISK:

  • Restaurant 1

  • Restaurant 2

  • Restaurant 3

When you add the Givex integration for each account you'll see the list of departments:

The departments show for the specific restaurant ID.

Reminder: When no boxes are checked it is pulling the sales from all departments.

  1. Go into each WISK account and select the corresponding department, then Click "Save"

    The "Restaurant 1" box is checked and an arrow points to the "Save" button
  2. Click "Yes" on the prompt to re-import sales

    An arrow points to the Yes button

  3. Re-import your sales from either a specific date or inventory

  4. The sales for just the selected department import into the account

Did this answer your question?