Retail and e-commerce teams running ERPNext hit a wall the moment marketing gets serious about promotions. ERPNext core ships Pricing Rule and a basic Coupon Code DocType, but they stop short of real campaign mechanics: there is no native buy-one-get-one engine, no tiered "spend more, save more" thresholds, no gift-card issuance and redemption ledger, and no clean way to scope an offer to a specific customer segment. Teams end up hand-keying discounts on each Sales Invoice, reconciling coupon abuse after the fact, and discovering that a promo that worked in the web shop behaves differently at the POS counter. The rules live in people's heads instead of in ERPNext.

We build a proper Frappe app — installed into your bench as its own module with versioned source — that layers a real promotions engine over ERPNext sales and POS. At its core is a Promotion DocType (rule type, priority, stacking policy, validity window) with child tables for conditions and rewards, plus Coupon Batch, Gift Card, and Gift Card Ledger Entry DocTypes. Coupon codes are generated in bulk (single-use, multi-use, or per-customer) with cryptographically random codes and server-side validation; usage limits and expiry are enforced in the database, not just the UI. BOGO, bundle, and tiered rules are evaluated by a whitelisted server-side method so the same logic runs identically whether the cart comes from the POS, a Sales Order, or a headless REST client.

Technically, the engine hooks into the transaction lifecycle through hooks.py doc events — validate and before_submit on Sales Order, Sales Invoice, and POS Invoice — to apply matched rewards, recalculate Sales Taxes and Charges, and stamp the applied promotion and coupon onto the document for audit. A whitelisted apply_promotions(doc) / validate_coupon(code, customer) API is exposed for the POS screen and any storefront, with a Client Script driving live feedback in the POS cart. Gift-card redemption debits the ledger atomically inside the invoice submit so balances can never go negative under concurrency. Segment targeting reuses ERPNext's Customer Group, Territory, and custom tags, and everything respects role permissions and permission-level (perm-level) field security so cashiers can apply but not author promotions. A scheduler event expires stale coupons and closes ended campaigns nightly. The app is built and tested against Frappe/ERPNext v15 and v16.

Because this is build-to-order, nothing is a shrink-wrapped download. We start with a scoping call to map your exact promotion types, stacking rules, POS workflow and reporting needs, then build against your version on a staging bench, run UAT with your team, and deploy to production with a rollback plan. Typical delivery is one working week from confirmed scope. You receive the full source in a git repository, documentation, a training session, and a post-go-live support window.