Update in Restaurant 365 Integration

Update in Restaurant 365 Integration

Introduction:

Restaurant365 maps the sales & receipt details from the POS system to General Ledger accounts using Sales Accounts and Payment Type Accounts which helps the customer to identifying problem areas with detailed reports and visualized trends.

This document explains about how the customer will transfer the data from Linga POS to Restaurant365.

Guide for uploading the file

·         The following file extensions are accepted while uploading the file - .CSV, .TXT, .DBF

 

·         Files can be exported and housed in the following locations:

o   R365 hosted FTP site

 

·         The following details needs to be sent to the restaurant 365

o   Sales

  File Name (Sales_locationid_MMDDYYYY)

  Column Names:

  Receipt Number (Check ID)

  Date (Date and Time of when check closed in local time)

  Server (Employee ID of server who took order)

  Tax Amount (Total amount of tax on ticket)

  Tip Amount (Total amount of tip on ticket)

  Number of Guests (Number of Guests served on check)

 

Note: The following columns should be included in the sales,

  File Name (Sales_locationid_MMDDYYYY)

  Column Names:

  Service Type (also known as Order Mode. Dine In, Take Out, Delivery, etc.) and the Variable character field length, Nvarchar(100).

  Revenue Centre (Text field containing set values from Linga stating the Revenue Centre where the order was placed like Banquet hall, Main dining area, Curbside etc.) and the Variable character field length, Nvarchar(50).

 

o   Sales Payments

  File Name (SalesPayments_locationid_MMDDYYYY)

  This file will include any Discounts / Promos / Comps / etc. as well as any Tender Types

  Column Names:

  Receipt Number (Check ID)

  Date (Date and time of when check was paid)

  Payment Type (Tender, Discount, Promo, or Comp Name)

  Amount (Amount Tendered)

  Credit Card Fee (Dollar amount of Fee charged for processing credit card) *

 

[* Indicates field is optional and not required]

 

 

o   Sales Details

  File Name (SalesDetails_locationid_MMDDYYYY)

  Column Names:

  Receipt Number (Check ID)

  Menu Item (name of item sold)

  Quantity (number of that item sold on a ticket)

  Amount (Amount of that item)

  Category (the category or the group of the item)

  Void (If Item was voided)

 

Note: The sales details should include the following columns,

 

o  File Name (SalesDetails_locationid_MMDDYYYY)

  Column Names:

  PLU (Optional) – Reference value for the menu item and the Variable character field length, Nvarchar(50).

  Item Modified - Reference to the menu item that is being modified and the Variable character field length, Nvarchar(100). Leave column empty if the row is for an item that is NOT a modifier.  Only populate if the row of data is modifying another item.  This field could reference the PLU value for a cleaner reference match, or if no PLU is included, then the menu item name would need to be provided as the value for this column of data.

 

o   Drawer

  File Name (Drawer_locationid_MMDDYYY

  Column Names:

  Type (Type of the Drawer Event that took place: i.e., 'Deposit Entered', 'Paid Out', 'Paid In' etc.)

  Amount (Dollar amount of Drawer Event that was processed)

  Description (Brief Description describing the Type: i.e., 'Deposit 1', 'Office Supplies') *

[* Indicates field is optional and not required]

 

o   Employee

  File Name: Employees

  Column Names:

  First Name

  Middle Name *

  Last Name

  Address 1 *

  Address 2 *

  City *

  Zip State *

  Phone Number *

  POSID

[* Indicates field is optional and not required]

                                   

o   Employee Jobs

  File Name: EmployeeJobs

  Column Names:

  Employee (EmployeeID)

  Pay Rate (Current Pay Amount)

  Job Title (ID)

 

o   Jobs

  File Name: Jobs

  Column Names:

  Job Title (Name of position)

  Job Code(ID)

  Pay Rate (Standard Pay rate for position) *

 [* Indicates field is optional and not required]

  

o   Time Card

  File Name (TimeCard_locationid_MMDDYYYY)

  This Export File will include that last 10 days of labor, and any adjustments made to time punches in the POS

  Column Names:

  Employee (ID that matches Employee file)

  Job Title (ID that matches job title file)

  Pay Rate (Rate of pay for employee for time punch)

  Date Worked (Date of when employee worked)

  Start Time (Time Employee clocked in)

  End time (Time Employee Clocked out)

 

Changes that needs to be implemented in Back Office

 

·         At the end of the ‘Close day’ in POS, the above-mentioned data will be sent to the restaurant 365 automatically.

 

·         Linga back office is providing an option to upload the data to restaurant 365 manually by selecting any specific date.

o   A new navigation ‘Export POS Data’ is added in the store level.

 

o   When the user clicks on the ‘Export POS Data’ link, the user should be navigated to the ‘Export Data Integration’ screen.

 

o   When the ‘Export Data Integration’ screen loads, it should have the following details

  Choose date

The user should be able to select any date from the date picker.

 

  Export data – button

On clicking this button, the above-mentioned data will be uploaded to the restaurant 365.

If the data is exported successfully, then a success message should be displayed.

If the data is not exported, then a failure message should be displayed.

 

o   Note: This link will be enabled only when the user has purchased license for this feature.

 

Screen Layout:

 



    • Related Articles

    • Enable PUC Integration

      PUC Integration workflow: Step 1: Placing an order.   Customer can login to the online order app/website and places an order via OLO. Step 2:  Receiving the order.  Once the order is received by the POS a pick-up code need to be generated. Step 3: ...
    • ValuTec Integration

      Implementation in the Back Office:               Page Navigation: My Stores >> Settings >> Payment               A new option “Valutec” should be displayed when the payment type SPPax is chosen.                 By default, this option will be in ...
    • Chowly Integration User Guide

      Note:  This information is available in a Word document and PDF file at the bottom of the page.  Introduction: This document explains the new integration partner – Chowly Integration. Requirement: A new integration partner - Chowly to be included in ...
    • Integrating Linga to QuickBooks Using Shogo

      Connecting Linga to Shogo You can have multiple stores within your Shogo account, and you will be prompted later in the process to set up each store you have.   Step 1: Go to https://app.shogo.io/login/auth   Register for a new account if you do not ...
    • Linga POS 2.1.3 Software Update

      New Features Overview Video New Features: Accept Multiple Currency’s New Order Type Additions Pending Modifiers Sales Recap Interface Update Shortcuts from the Order Screen Add Tax ID to a Tax-Exempt Check Caller ID Add a Logo to Guest Check ...