Case study · B2B SaaS · Sales reconciliation
Giving restaurants more control over sales reconciliation
My role: Product Manager; Senior Product Manager for later iterations, partnering with the Accounting and Reporting PM, architecture, lead designer, developers, and QA.
The business need
Orderly began as food cost management software for operators with 1–5 locations. Enterprise rearchitecture and the RASI acquisition broadened the product into accounting, shifting investment toward foundational capabilities and migration requirements without a consistently defined ideal customer profile.
Following the RASI acquisition, Back Office needed a sales reconciliation module to support customer migration. RASI customers actively reconciled sales and could not move to our platform without that capability.
The module also needed to post sales activity to the general ledger—an essential capability for selling restaurant accounting software.
This was a new accounting domain for me. I had previously owned sales reporting for food-cost management, so I partnered with the Accounting and Reporting PM to understand how sales, taxes, tenders, discounts, and cash differences flowed into financial reports.
Designing for customer control
RASI customers relied on internal teams to configure their sales pages and map POS data. I wanted customers to manage that setup themselves while supporting accurate accounting treatment and general ledger posting.
I proposed a sales-item model between POS data and general ledger accounts, then presented it to engineering and architecture for review and sign-off.
This model allowed separately named items to share a general ledger account while carrying different debit or credit treatment. Gift card sales and gift card redemption, for example, needed distinct categories and opposite accounting treatment despite using the same GL code.
Customers could create readable sales categories, assign accounting treatment, organize their reconciliation page, and map POS data themselves.
Balancing flexibility and accuracy
Giving customers configuration control introduced a risk: they could assign debit or credit treatment incorrectly.
I worked with stakeholders to agree on a correction path. Customers could archive an incorrectly configured sales item and create a replacement. This provided a way to correct setup mistakes while retaining the flexibility of customer-managed configuration.
Adapting beyond the initial customer cohort
The initial release supported daily reconciliation with weekly posting. Our early research focused on RASI customers, who were accustomed to a weekly workflow.
As we began selling the accounting offering to a broader customer base, feedback exposed a different need. Waiting until week-end to post sales delayed bank reconciliation for customers who wanted to reconcile deposits throughout the week.
That feedback drove the next iteration. In summer 2026, we launched daily posting, improved the interface, and added draft saving so customers could review and approve sales when ready.
Measurement context
Initiatives were not consistently tied to measurable business objectives. For this work, the established result was a launched, used capability enabling migration and accounting sales. Incremental revenue, retention impact, and time savings were not established.
The result
The module launched and was actively used by customers, providing the sales reconciliation and general ledger posting capabilities required to support RASI customer migration and the broader restaurant accounting offering.
Verbal customer feedback relayed through support indicated that daily posting helped users reconcile bank deposits sooner and stay organized. These benefits were not quantified, and satisfaction was not formally measured.
Exploring simpler setup with AI
Manual setup remained time-consuming. I built an internal AI prototype that proposed sales categories and accounting mappings, surfaced uncertainty, and guided users through setup.
Accounting subject matter experts verified its outputs. The prototype remained an experiment when my tenure ended.
What I learned
The initial research reflected the habits of migrating RASI customers. As the product reached new buyers, we learned that those habits did not represent everyone’s needs.
The experience reinforced the importance of including both migrating customers and new buyers in discovery, then revisiting workflow assumptions as the market expands. It also showed how product modeling could give customers meaningful control over a complex accounting process.