Versions Compared

Old Version 14

changes.mady.by.user Debrupa Datta (Unlicensed)

Saved on

compared with

New Version 15

changes.mady.by.user Debrupa Datta (Unlicensed)

Saved on

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 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
titleE-Commerce Sale: Receiving 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.



Info
titleE-Commerce Sale: Shipping / 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 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
titleE-Commerce Sale: GST charge in case of Export can now be configured Version 12.8.0 - 2.8.0


From now Users can mark the LUT status in the GSTIN master. Accordingly while creating e-com transactions, GST calculation will be done.

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): Already supported.


Info
titleE-Commerce Sale: Introduction of Channel Master Version 12.8.0 - 2.8.0


  • Now with the Channel Master concept the user will have to select channel instead of mop control a/c.

  • Commission bill can be posted under the same channel SL which automatically gives the net receivable from the channel.


Note

Note: Existing other type of sub-ledger (which has e-com transactions done against them) with AR/AP ledger tagged to it are automatically migrated to the channel class (master).


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): Provisions done as mentioned above.



Note
titleE-Commerce Sale: Channel wise sales ledger now possible Version 12.8.0 - 2.8.0


From now “Sales ledger” field will be available in channel master. Previously, e-com sale transaction was done in the “Consignment Sales” ledger tagged in OU.

Note

If the “Sales ledger” field is provided, the system will post the sale into that “Sales ledger” only instead of OU. This gives a flexibility to the users to maintain even channel wise sales (like amazon, flipkart, etc.).


Impacted Modules:

  • UI / Excel Import / New Public API / ERP <> OMS (Browntape): Ledger will be populated as per the new flow.

  • Old API (used for existing e-com OMS integrations): Ledger will be populated from OU (old flow).



Info
titleE-Commerce Sale: Configuration 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 import, then Ginesys scheme document number was used.

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

Changed behaviour:

  • 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 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 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.


Info
titleE-Commerce Sale: Recalculate tax while posting via API now configurable Version 12.8.0 - 2.8.0

 Now a flag has been added in channel master called “Recalculate Tax”. If this flag is enabled, the system will automatically recalculate the tax, else, the system will post the tax values supplied in the API call.

Impacted Modules:

  • 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, i.e., always recalculate.


Info
titleE-Commerce Sale: Additional visible changes applicable only for ERP <> OMS (Browntape) connected app integration Version 12.8.0 - 2.8.0

Retail Order

Online e-commerce order is posted into ERP as a Retail Order. Types of retail orders can be New (first sale order), Return, Exchange (Forward order against return).

This is a view only menu as retail orders can be created only via ERP <> OMS (Browntape) connected app API. Reason: An entire workflow is mapped with our OMS platform like reservation, picklist, confirmation, etc. Such operations of retail order is not possible from frontend.

Channel Master → “Is marketplace” field

This field is applicable only when channel is being configured for ERP <> OMS (Browntape) connected app integration.
If this field is set to “No”, then MOP with ledger needs to be specified while creating the channel. The usage of MOP is while pushing own web store’s retail orders which in turn creates deposit journals.