Please enable JavaScript to view this site.

RanceLab Software User Help

Navigation: Release Notes

Release Notes RanceLab Release 2.814

Scroll Prev Top Next More

Download Link

You can download the update package by clicking below

Rancelab Release 2.814

Integration with Plutus or other solution to accept credit card in POS.


Required to integrate the EDC machine with POS to eliminate the user errors while entering the amount in the EDC machine manually.


Solution: EDC Device (Plutus) Integration

Step1: Setting up the software for Plutus

Step2: Setting up RanceLab for Plutus


Setting up the software for Plutus:

‘CentralizedPADController' application: The installation of this software is to be done by

the Plutus Support Team.


Setting up RanceLab for Plutus: Setting up Plutus is straightforward in RanceLab.

1.In Mode of Payment Master (M A M), create a  MOP type (eg.: Credit Card )

2.Create MOP under Vendor 'Plutus' and add that MOP in sale option.

3.When you press any key on Plutus MOP in the tender screen, it will send the control to Plutus EDC and you need to complete the transaction there.

4.On successful payment, it will show

Please save data, don't update transaction,

else it will display the following error on the screen “Error getting data from Plutus application, failed to process transaction. Please retry.”


Plutus Integration will work in the following modules while doing payment in the tender screen.

1.Property Management Payment Screen

2.Sale Invoice (STT & STS)

3.Prepaid Card Transaction (Fill & Refill Mode).


For communication between RanceLab and Plutus Device, ,'CentralizedPADController' application should be open and check the connectivity by pressing 'Test Print'.

In Prepaid Refund mode, it will not work. Payment is not allowed in this MOP. But it will work in Prepaid Fill & Refill mode, here we have to enter the value manually and then save it. Then it will show the transaction is successful.


Template Function to select a bunch of items in one go to speed up the entry of inventory vouchers.


1.During entry in stock transfer indent or physical stock voucher, we need to select many items manually every day, that might be time consuming and erroneous.

2.While selling gift baskets in a bakery with the different items in it with different tax. With template function, you can now select those items in one go.

3.Physical stock entry usually has a fixed number of items. The operator is required to just fill in the qty. You may use the template function to speed up the process.



The template system is used to create a bunch of items to be used during the entry of inventory vouchers.


Template System:

To Create a Template:  Open any supported module. Select required items and then Save Template (Alt + J)

To Modify a Template: Load Template > Modify > Again Save Template with the same name.

To Use an Existing Template:  Load Template (Alt+K): It will show the list of available templates > select the required > it will populate the items.

The load function can be used in running invoice also.

To Delete a Template:  Del Template (Alt+X): It will show the list of templates > select template > It will ask "Do you want to delete?”

To Print a Template:  Prn Template (Alt+Y):  It will show the list of templates > select template > It will print that particular template. You may use this print to stick on the box as a packing list.


Supported Modules: The Template Function is available in the following modules:

1. Physical Stock

2. Stock Transfer Indent

3. Sale Order / Sale Invoice (STT and STS) / Sale Challan



Touch POS: If the item in the template is not on the menu, it will not load because we must have a KOT printer defined in order to make an STT sale.

Item Active or Inactive: There is no check for the active/inactive item while loading the template.

You may also define the qty for each item while creating a template.

If we save any touch POS template without qty then it will load the template with minimum 1 qty.

The template data travels and works in a multi-location environment just like masters.


Required Integration with UrbanPiper to receive data from Swiggy and Zomato ordering apps.


Need Integration with UrbanPiper application, to fetch the online order from third party online ordering apps like Zomato, Swiggy, etc.



Home Delivery or Pick up Orders will be placed at the UrbanPiper portal from different third-party online ordering apps like Zomato, Swiggy, etc.

Orders placed here will be pulled by RanceLab in a specified duration for the related locations.

The rest of the Order processing activity will be done in RanceLab like accepting the order, Dispatch, Delivered through Home Delivery Module.

The status of the order will be updated in the UrbanPiper portal.


The parameters required for this integration are defined in a JSON format.

In RanceLab this JSON will be saved in Global Option (TAG)


{"UP-Settings-JSON":{"Pull-Request-in-Second":"30","Fetch-Order":"", [^] "Order-Status-Update":"", [^] "Authorization":"apikey biz-adm-pos-NAYzrWIGTykF:XXXXXXXXXXXXXX","Locations":[{"LocationCode":"001","Station":"Server","Menu":"Restaurant Menu"},{"LocationCode":"002","Station":"Server","Menu":"Restaurant Menu"}],"Taxes":[{"UP-Tax":"12% GST","FR-Tax":"Cgst+Sgt @12%"},{"UP-Tax":"5% GST","FR-Tax":"Cgst+Sgat @5%"}],"MOP":[{"Channel":"Zomato","FR-MOP":"Zomato Cash On Delivery"},{"Channel":"Swiggy","FR-MOP":"Swiggy"},{"Channel":"web", "FR-MOP":"Cash On Delivery"}]}}


Description of JSON elements:

Pull-Request-in-Second = define duration second for searching the orders in the UP portal.

Fetch-Order = Enter Link provided by Urban Piper

Order-Status-Update = Enter Link provided by the UP.

Location Code = Enter the Location code of fusion for which order will be placed.

Station = Enter station name of the location server

Menu = Enter the menu name whose items are mapped with UP.

Taxes: Map tax of UP with Fusion Tax name which is applied to the menu products

Channel = Zomato,Swiggy,Web

FR-MOP = Equivalent MOP name of Fusion for each channel


Require Channel Name - Zomato or Swiggy and Merchant Id in KOT Heading / Bill Print Heading


Merchant ID is used by the Swiggy driver to collect the delivery order from the shop. In FR we record the Order ID of UrbanPiper which is different from merchant ID. Users are not able to track the order when a driver comes to the billing counter to collect the order.


We are now saving channels / numbers in the existing channel field (‘Web’).

This field will be printed (if not blank) in KOT and Bill in BOLD.

KOT popup should have an option to cancel the order.


There should be an option to Void KOT in the KOT popup screen when receiving orders from the call center.



In the KOT popup screen, the Close button is replaced with VOID.

Currently, the close button just postpones the current KOT and shows you the next KOT if any.

Now the VOID button will void the entire order and send out cancel notification to the third-party app.

The void button will also print the VOID KOTs.

After receiving the VOID status from the third party app, void KOT will be sent to print, and it will stop popping up the void KOTs once the order is cancelled at the third party.