Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 Excel can be generated from that store and can be imported in GINESYS using new import excel 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

...

    • Business Scenario - Consider a scenario where you list your products in 'Flipkart'. Also, you send the goods to a Flipkart's warehouse, i.e., 'Bhiwandi Warehouse' for order and dispatch.
    • Key Highlights -
      • We will create a customer (consignment) and then unmanaged customer's site for such outlets.
      • Tax/VAT posting shall be done as per the mode specified in customer master.
      • Customer A/C shall be debited until the transaction amount is received by Head Office.
    • Process Detail -

    • GINESYS user transfer's stock from its warehouse to customer/marketplace site location.
    • Consumer purchases goods from marketplace and the marketplace delivers those items from their warehouse itself to the consumer.
    • Marketplace then shall share the sale information in excel Excel format to GINESYS user who in turn shall import using new import excel Import Excel option for that marketplace site.
    • Sample Values: 
      Site Name - Bhiwandi Warehouse - Flipkart 
      Customer Name - Flipkart

...

  • Process Detail 

    • GINESYS exposes stock information of the organization site to third party 'E-commerce Aggregators'.
    • 'E-commerce Aggregators' then further exposes same stock information to all the marketplaces / own web-store.
    • Consumer purchases goods from marketplace/own web-store.
    • This order information will get available in e-commerce aggregator website via their integrations with marketplaces/own web-store.
    • Order processing to dispatch/invoicing needs to be done in E-commerce Aggregator's website.
    • After invoicing, they will generate an excel Excel which can be imported in GINESYS using new excel import Excel Import option for that organization site.
    • Sample Values: 
      Site Name - E-commerce Fulfillment Center 
      MOP Control A/C - Flipkart Control A/C

...

Info
titleManual Scheme Document Number allowed (Version 12.8.0 - 2.8.0)


Manual scheme document number is now allowed. From now -

  • User can select manual numbering and provide the number against which the document needs to be imported in UI.

  • User can select manual numbering and map the document number column In excelExcel.

Info
titleNote

For using the manual number, the user needs to first tag the manual number to the menu.

Impacted Modules:

  • UI / Excel Import: Provisions done as mentioned above.

  • New Public API / ERP <> OMS (Browntape): Always manual.

  • Old API (used for existing e-com OMS integrations): Always manual.


...

Info
titleReceiving good and damage returns in separate stock points (Version 12.8.0 - 2.8.0)


User can now provide the stock point at the item level when both the good and damage products are being received. If stock point is provided at item level, the stock impact for that item will take place in that stock point, else will take place in the header stock point.


Note

This stock point has been added for only for return items.


Impacted Modules:

  • UI / Excel Import / New Public API / ERP <> OMS (Browntape): Provisions done as mentioned above.

  • Old API (used for existing e-com OMS integrations): Not possible, works in existing way.

The Path in the VM is - Sales & Distribution > Setup > OMS App Application > Select a Site from Available Site and assign it.


Info
titleShipping / other charges with dynamic (max) tax is now possible from Excel Import / UI (Version 12.8.0 - 2.8.0)


Now “Dynamic Tax” field has been added at the item level and can be used from both excel Excel import and UI.

In GST law perspective, if shipping charges are treated in the aforementioned way, it comes under a “Mixed Supply” case.

Impacted Modules:

  • UI / Excel Import / New Public API / ERP <> OMS (Browntape): Provisions done as mentioned above.

  • Old API (used for existing e-com OMS integrations): Not possible, works in existing way.


...

Info
titleConfiguration added to specify which number to pick for GST returns (Version 12.8.0 - 2.8.0)


Existing working: The number used while creating the transaction was picked up for GST return purpose.

  • If created via UI or excel importExcel Import, then Ginesys scheme document number was used.

  • If created via API, then marketplace / OMS scheme document number was used.

Changed behavior:

  • Document created using ERP scheme document number - The same number will be used for GST returns.

  • Document created using manual number / marketplace number / OMS number -

    • A flag in channel Channel master “Allow ERP to generate auto GST doc number“ has been added.

    • If this flag is set to “Yes”, the system will auto create a number and put in GST doc number field which ultimately will be used for GST returns. However, payment reco reconciliation can be done based on transaction number itself.

    • There are two system defined scheme numbers for this purpose, i.e., for Tax Invoice and for Credit Note.

...