v2.14.0

Payments

New Feature

Split Payments: Pay for One Order Across Multiple Methods

Customers can now pay for a single order using more than one payment method, across more than one transaction, online or in store. A sale no longer fails just because one card, wallet, or UPI account cannot cover the full amount. The order stays partially paid until the balance is collected, then it is placed automatically.
Impact: high-value orders that used to fail at payment now go through. Earlier, a customer short on any single method had to drop the order, and staff at a counter could not close a bill that needed part cash and part card. Both of those now complete, which lifts checkout completion on larger baskets and lets merchants take payment combinations they had to turn away before.

• Configure & control: Turn Split Payments on per sales channel and business unit, and set how many splits are allowed, a minimum value per transaction, and the window to complete payment. Choose which methods are allowed on the first transaction and on the rest.

• Pay flexibly: Split a single order across cash, card, UPI, net banking, or wallet. In-store payments are collected by staff, and the receipt shows the breakdown by payment mode.

• Refund accurately: Collect the balance or cancel at the order level. If payment is not completed in time, the system cancels the order and refunds only the transactions that succeeded, using the right refund mode for each payment method.

Learn More

Order Management System

New Feature

Order Review - Validate Orders Before Fulfilment Begins

Not every order should go straight into fulfilment. A B2B order might be firmed up with the buyer and cleared by finance first; a pharmacy order needs its prescription verified; a high-value or custom order needs a final confirmation; a flagged or high-risk order needs a manual check before it proceeds. In each case someone has to review the order before it moves, and without a way to hold it, the order can be confirmed, picked, and packed the moment it's placed, before anyone has validated it. Unwinding that afterwards means cancellations, reversals, and rework.

Fynd OMS now lets merchants add a review checkpoint before an order enters processing. When enabled for an application, new shipments open in an Upcoming stage instead of Placed, an internal stage the customer never sees, since the storefront always shows the order as Placed. A review team can adjust the order, reduce quantities, remove items, or verify details, and move it to Placed only once approved, at which point the store team confirms, packs, and dispatches as usual. Merchants control this per application under Order → Preferences, off by default, so nothing changes unless they switch it on. Orders can also auto-release to Placed after a set duration in minutes, hours, or days, for teams that prefer a time-boxed hold.
With Order Review, merchants can:

• Hold new orders for review before any fulfilment effort is spent

• Adjust quantities, remove items, or verify details before releasing to processing

• Auto-release after a set time, or move orders forward manually

This means the work of confirming, picking, and packing goes only to orders that have already been reviewed, cutting the cancellations and rework that come from processing an order before it's validated, and letting any business that needs a review step run it natively instead of working around it. Order Review is now available in Fynd OMS.

New Feature

Final Cancellation — Cancel an Order Yourself, Even After Confirmation

When an order needs to be cancelled — the customer changed their mind, the address can't be served, or no store can fulfil it — every step toward dispatch adds cost. Cancelling a shipment in OMS today reassigns it to the next serviceable store and ends it only once every store is exhausted, so an order that should stop keeps moving: inventory stays committed, the refund is held up, and effort goes into something that was never going to ship. And once a shipment is confirmed, the merchant can't cancel it at all — the request goes to Fynd's support team, which means a ticket, a wait on another queue, and a customer holding on while the order keeps moving. A large share of cancellations land exactly there, after confirmation — a routine cost, not an edge case.
Fynd OMS now adds a direct, final cancellation — no reassignment, no cycling through stores, and no dependency on support. A merchant can end a shipment outright, for a customer or their own store, right up until it goes out for delivery — including after confirmation, the exact point where a support ticket used to be the only option. Cancel the full shipment or specific items, with the rest of the order continuing as normal; each cancellation captures a reason and optional remarks, and refunds, inventory, and invoicing are handled automatically. Access is role-controlled — Company Admin and Full Access roles, plus any custom role a merchant grants it to.
With final cancellation, merchants can:

• End a shipment outright, with no reassignment — releasing committed inventory and starting refunds sooner

• Cancel at any point up to out-for-delivery, including after confirmation, without a support ticket or a wait on another team

• Stop an unwanted order before it ships, rather than letting it dispatch and return as an RTO

This moves cancellation out of the support queue and into the merchant's own hands: instead of reassigning an order store to store, or raising a ticket and waiting once it is confirmed, teams end it in a single action the moment it should stop — so effort, inventory, refunds, and turnaround aren't held up by orders that were never going to complete, or by a support team's response time.
Final Cancellation is now available in Fynd OMS.

‍