Explore

PRD - OMS invoice sync

Context -

Seller tax invoices are essential for sellers to process taxes and reconcile net sales. Currently, these invoices are accessed via a download option within the payments tab of the seller panel.

However, brands typically do not consume this data from the seller panel, as their processes are primarily managed through OMS. This results in two key issues -

OMS clients generating their own invoices for brands, often leading to amount mismatches.

Difficulty in linking order-level invoices to the brands' ERPs, requiring significant manual intervention.

Objective -

Enable order-level invoice sharing with OMS through the following capabilities:

Push order-level invoice details to various OMS platforms in JSON format.

Provide a reconciliation API for OMS to fetch invoice details for a specific sub-order number in case of a push event failure.

Required changes -

Push API for sub order num level invoices -

Create a push API that shares invoice metadata with OMS whenever an order is manifested along with manifest label

Invoice metadata to be shared -

Sub order number

Sold by - Supplier name and address

GSTIN

Purchase order no.

Invoice no.

Order date

Invoice date

Bill to / Ship to - User details

Payment transaction ID

Mode of payment

Date & Time

Invoice value

Description

HSN

Qty - Quantity

Gross Amount

Discount

Taxable value

Taxes

Tax slab

Taxed amount

Total Amount

Pull Request for Invoice Reconciliation -

Develop capability for OMS clients to fetch invoices for specific sub-order numbers on demand

Ensure that invoices are shared exclusively for orders associated with the requesting seller in the OMS

Backward compatibility -

Ensure invoice details are sourced from the primary service to automatically handle any changes to invoicing, such as pay-before-delivery scenarios, for seamless integration with OMS

Backend invoicing adjustments like PBD / BMSM are accounted for

Approach decision -

Two potential approaches for syncing invoice JSON metadata with OMS -

At Order Creation:

Pros: Simplifies integration for OMS 3Ps, as invoices are generated at order creation and can be directly linked to the brand's ERP

Cons: Adds complexity on the platform side, as backend invoicing adjustments (e.g., post-order discounting or payment method changes) require an invoice update workflow and cross-team collaboration

In-house effort -

[Recommended] At Order Manifestation:

Pros: Easier for the platform to implement, allowing flexibility for pricing experiments and other changes between order creation and manifestation

Cons: Requires OMSs to adapt their workflows, as it deviates from likely default invoice generation processes

In-house effort - 2 sprints

Scale up and roll out -

Invoices will be pushed for all sellers operating via OMS.

OMS partners must be informed about the changes in the payload to ensure they use the correct fields to generate PDF copies of invoices for brands.

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.