In the current retail market scenario, there are different channels through which a sale is executed, i.e., Retail Stores and E-commerce Websites/Apps. However, GINESYS had a provision to enter sale information of only Retail Stores and not E-commerce sale. From the Ginesys HO Version 11.111.0, it is possible to update the same.
...
- Business Scenario - Consider a store which is owned by you but it is an exclusive brand outlet of brand 'ABC'. Due to this, 'ABC' brand shall enforce their software which shall sync information to their database. Previously, even if you wanted to keep your software, i.e., GINESYS updated with the receive/sale information of that store, there was no such provision for the same. Now after this update you can do so by creating a new organization site for that store and do normal Goods Receive and post the sale information by using the process specified below.
- Key Highlights -
- We will create an Organization Site (OS-OO-CM) for such outlets.
- Tax/VAT posting shall be done in exclusive mode.
- MOP Control A/C shall be debited until the transaction amount is received by Head Office.
| Note |
|---|
Note: MOP Control A/C will be sub-ledgers of "others class" having AR/AP ledger tagged to it. |
- Process Detail -
- On purchase of goods for that store from the Brand, goods receive document shall be created manually by connecting to that organization site.
- On sale of goods from that store in the Brand software, an excel can be generated from that store and can be imported in GINESYS using new import excel option into that organization site.
- On importing the sale, MOP Control A/C shall get debited and on receipt of money at HO, it can be set-off in AR voucher or via document adjustment.
- Sample Masters:
Site Name - Elgin Road Store (ABC Brand)
MOP Control A/C - Elgin Road Store (ABC) Control A/C
...
| Info | ||
|---|---|---|
| ||
This change is applicable for scenarios where the brand brands are using their logistics for shipping(not using marketplace logistics) and there is a Cash on Delivery (COD) or Pay on Delivery (POD) transaction. Current accounting in retail sale used to debit the “MOP Control A/C” or Channel (renamed, details mentioned below separately) even though the amount was to be received from the transporter due to COD/POD. Now while creating the transaction, if COD/POD amount is provided, transporter selection will be mandatory, and the transporter will be debited instead of channel. There can be partial COD/POD cases as well. In such case, upto the COD/POD amount transporter will be debited, for rest of the sale amount channel will be debited. Impacted Modules:
|
| Info | ||
|---|---|---|
| ||
Delivery details can now be captured along-with the retail sale transactions like awb number, shipping date, delivery date and transporter. These are non-mandatory fields and just for information capturing purposes only. Impacted Modules:
|
...