Skip to content

PRDs: Commerce

In recommended reading order, top-down. Status is synced from Plane on every build - the all-module view lives on the PRD Register.

#IDNameDescriptionSurfaceStatus
1PRD-ORG-001Organizer & merchant
  • Product requirements for standing up a business structure
  • onboarding in one step, the organizer/merchant principles (virtual brand vs legal unit), saving a merchant together with its channels and categories, slug checks, and role-filtered launchpads
Back OfficeClientReady to dev
2PRD-SC-001Sale Channels
  • Product requirements for Sale Channels
  • each merchant sells through multiple channels (dine-in, takeout, delivery), each channel decides its own stock-pickup location and print configuration, has a default channel, and cannot be deactivated while it still has active orders
ClientSale POSBack OfficeReady to dev
3PRD-CAT-001Sale Categories
  • Product requirements for sale categories
  • each category gets its own icon and color for instant recognition on the POS, can be arranged into a tree up to 8 levels, with a reusable icon-color picker other forms adopt
ClientReady to dev
4PRD-FLR-001Table & floor allocation
  • Product requirements for the restaurant floor plan
  • an owner or manager designs a named floor layout as a tree (floor / room / table) on the Client page, each table carrying its own capacity, placement and style, while the Sale POS occupies tables against dine-in orders, shows live free/busy status, finds free tables, transfers a party between zones, and keeps an allocation snapshot on the order
ClientSale POSReady to dev
5PRD-RCP-001Receipt templates
  • Product requirements for merchant- and channel-scoped receipt templates
  • a named, locale-aware layout authored on the Client page or in Back Office from a fixed block vocabulary (text, line, image, line-item table, barcode, QR, grid), validated on save, exactly one default per (scope, language), with POS only syncing the latest template and rendering it to a thermal-printer raster at checkout per the paper widths the platform supports (58mm/80mm, extensible)
ClientSale POSBack OfficeReady to dev
6PRD-RTL-001Retail Business Type
  • Product requirements for the Retail business model on BANA
  • explicit business-type selection when creating a merchant, category templates by retail sector, a counter selling mode at the POS, and correct invoicing and tax for retail merchants
Sale POSClientBack OfficeReady to dev
7PRD-BOP-001Merchant Onboarding (Back Office)
  • Product requirements for the Back-Office onboarding flow
  • where an operator signs up a new client end-to-end on one guided screen: the organizer, the owner account, the first merchant, and a subscription plan, optionally pre-filled from an inquiry, after which the client is ready to sell
Back OfficeReady to dev
8PRD-MER-001Merchant Management (Back Office)
  • Product requirements for the Back-Office Merchant Management screen
  • where an operator finds merchants across organizers, creates new ones, edits each merchant's profile and lifecycle, and configures a merchant's payment providers, payment settings, and print template
Back OfficeReady to dev
9PRD-CAT-002Category Template Configuration (Back Office)
  • Product requirements for the Back-Office category-template configuration
  • the shared, industry/sector-scoped starter-category list Operations authors, which onboarding copies onto a new F&B or Retail merchant as its own editable categories
Back OfficeReady to dev

Proprietary and Confidential. Unauthorized copying, distribution, or use of this software is strictly prohibited.