How Pero solved multi-channel inventory chaos with Fynd POS

What is Fynd store management platform?

The Fynd store management platform is designed to simplify running in-store retail operations by combining point-of-sale billing, inventory management, stock transfers and reporting all in one system. It’s built with a mobile-first approach, allowing staff to bill customers and check stock right from a tablet or phone, rather than being tied to a fixed counter. For brands that also sell through partner stores, the platform tracks and reconciles stock at those partner locations too.

At Pero, the focus of the implementation was to standardize billing and inventory across its own retail studio and to bring its Sale-or-Return (SOR) partner network featuring partners like Good Earth, Ogaan, and Pernia's Pop-Up Shop - onto a single system for better stock visibility and reconciliation.

The challenge: No single view across platforms

<Graphic>

Reference

Pero’s retail and SOR operations had expanded faster than the back-end systems could keep up. Both the studio and partner locations were mainly managed using Excel, which led to several ongoing issues, as the brand shared:

No centralized visibility

Each channel kept its own records, with no unified view of stock across all locations.

Manual reconciliation

Comparing studio stock to partner stock was a manual process prone to errors.

No real-time stock insight

There was no way to track inventory movement or sales in real time at any location.

Heavy manual dependence

Core processes depended heavily on manual effort, which slowed things down and introduced inconsistencies.

Fragmented reporting

Without a unified reporting system, compiling a complete picture meant piecing together data from multiple sources.

No structured customer data

The brand lacked a systematic way to capture customer information or focus on building customer retention.

The solution: Platform built to replace disconnected systems

<Graphic>

Every location configured as its own stockpoint

The warehouse, Pero’s retail studio and SOR partner outlets are each individually configured within Fynd.

146 SKUs, fully structured in one place

Jackets, dresses, tops, shirts and bottoms - all SKUs include their HS code, tax rules, pricing, and barcode/GTIN information.

Stock enters through one QC-checked process

Goods are inspected and recorded at the warehouse before being added to sellable inventory.

Assisted selling and POS billing at the studio

The checkout process supports mixed payment methods and sends digital receipts as standard.

Outbound transfers, reconciliation and invoicing with partners

Stock moves to partner locations, with regular sales reports feeding into reconciliation and invoicing.

Returns processing for both studio customers and SOR partners

IInventory is automatically updated once returns are confirmed.

One reporting layer instead of manual Excel consolidation

Daily sales, monthly store performance, inventory aging and SOR partner performance are all pulled from a single source.

How it works, day to day

For store staff

Sales begin by pulling up or creating a customer profile using their mobile number. Staff scan or search for the product, note any customizations, and select whether the customer wants to carry out or have the item delivered. The checkout supports mixed payment modes like card or payment links, and sends digital receipts by SMS or email. The assisting staff member is tagged to the sale for performance tracking.

For the store manager

Stock arriving at the studio comes through transfers from the warehouse, accompanied by a dispatch note and confirmed upon receipt. Any mismatch between what was sent and what arrived is flagged automatically, rather than being discovered weeks later. Returns are managed through an invoice lookup, quality check and options for exchange, refund, or store credit, with inventory updated immediately upon confirmation.

For the HO/ops team

Instead of juggling multiple spreadsheets, the team works from unified dashboards showing daily sales, monthly store performance, inventory aging, and SOR partner performance. Specifically for partners, reconciliation follows a clear formula: opening stock plus transfers in, minus sales, minus returns equals closing stock. Any discrepancies are flagged before the month-end invoice is issued.

Rollout timeline

The implementation followed a confirmed 15-working-day plan:

How Pero’s product master changed

Built to scale beyond one studio

Pero’s journey is one many brands can relate to - the retail side grows, the partner network expands and eventually, Excel just can’t keep everything together anymore. The real breakthrough wasn’t solving just one pain point; it was bringing the studio and the Sale-or-Return (SOR) network onto a single platform. This shift allowed stock, sales and partner performance to be viewed as one connected business, rather than six separate, disconnected pieces.

That’s an important takeaway for other brands in a similar spot: the goal isn’t about having a bigger spreadsheet or a slightly better manual process. It’s about having a system designed to grow seamlessly, without needing to be rebuilt every time a new store or partner comes on board. For Pero, this means the next studio can simply launch on the existing stockpoint setup and product master - no extra setup required. For any brand seeing its retail and SOR operations outgrow their current tools, that’s a clear sign it’s time to move beyond spreadsheets for good.

FAQs

Which Fynd capabilities were deployed? Store OS POS and inventory management, covering tenant/stockpoint setup, product master, inwarding, B2C billing and returns, B2B SOR workflow and reconciliation, and MIS reporting — all standard (non-customised) Store OS capabilities.

How long did the rollout take? 15 working days, from kickoff to go-live, followed by a hypercare and stabilisation period.

What changed in daily store operations? Billing, stock transfers, and returns moved from manual, Excel-tracked processes to a single system with built-in checks — mismatches on transfers are flagged automatically, and reconciliation with SOR partners follows one consistent formula instead of ad hoc matching.

What should a similar retailer evaluate before implementing this setup? Whether the standard (vanilla) Store OS feature set covers their workflow — Pero's rollout was scoped to standard capabilities, with any customisation beyond that chargeable separately. Retailers with a large SOR network should also plan for how partner sales reports will be ingested (manual template upload vs. an automated connector) and get the product master cleaned up before go-live.