Marg ERP WhatsApp Integration - Pharma Dispatch, Batch Expiry & DL Invoicing

Yes. Every DL-compliant invoice delivered over WhatsApp carries the seller's Drug License number, the buyer's Drug License number (where captured in Marg's party master), the batch number and expiry date per line item, and the manufacturing date. This is not optional formatting — it is the regulatory requirement for pharma B2B invoicing under Drug and Cosmetics Rules, 1945, and it is what chemists in your downstream chain need to receive to comply with their own record-keeping under Form 2 / Form 8. Generic ERP-WhatsApp connectors that only render invoice number and amount do not meet this bar.

Yes. The connector scans Marg's batch master daily and generates WhatsApp broadcasts to your retail chain at 30, 60, and 90 days before expiry. Each broadcast is filtered by which chemists have received that batch recently (based on Marg's dispatch history) so you are not spamming chemists who no longer hold the stock. The template includes the batch number, expiry date, and a link to Marg's return-and-replace workflow. This is a substantial revenue-recovery play — pharma expiry losses across the Indian retail chain run into thousands of crores per year, most of it recoverable if the retailer is alerted in time.

Multi-godown Marg installations are common for pharma distributors — one Marg company with 5-20 godowns across a state. The ERPPlugs Marg-WhatsApp connector supports binding each godown to its own WhatsApp Business phone number, so a Mumbai warehouse dispatches with its own WABA and a Nagpur warehouse dispatches with its own. Party masters, batch registers, and stock reports remain per-godown as configured in Marg, and the ERPPlugs dashboard shows dispatch and delivery stats per godown. This is essential for C&F agents who cannot cross state lines with a single sender phone.

Yes, both editions are supported. Marg SQL Server (used by larger distributors with 50+ concurrent users) is connected via ODBC with SQL Server Authentication. Marg Access (used by single-branch chemists and C&F agents with smaller teams) is connected via the Access ODBC driver. The signed Windows agent auto-detects which edition is installed and uses the appropriate connection profile. Both editions are read-only from the agent's perspective — nothing is written back to Marg unless explicitly configured (for example, posting a chemist reply as a note on the Marg party ledger).

Yes. If Marg is integrated with your shipping partner (Shiprocket, Bluedart, Delhivery, DTDC, or a manual courier), the ERPPlugs Marg-WhatsApp connector picks up the AWB or tracking number at the point of GRN creation and renders a live tracking URL in the WhatsApp dispatch confirmation. Chemists tap the link and see live courier status. For carriers not natively integrated with Marg, the tracking URL can be pulled from a supplementary CSV or from a Zapier/Make workflow that watches your shipping partner's dashboard.

Yes. Certain pharma categories — including some vaccines, injectable formulations, and life-saving drugs — are subject to reverse-charge mechanism under GST. When Marg flags an invoice as RCM, the ERPPlugs Marg-WhatsApp connector automatically uses a template variant that clearly labels the buyer's RCM liability, includes the correct GSTIN pair, and omits the CGST/SGST/IGST breakup lines that do not apply. This prevents the common downstream confusion where a chemist receives an RCM invoice and treats it as forward-charge, mismatching their books.