01
The problem
Getting paid meant leaving FloatMerchant or using a half-finished invoice screen. There was no solid way to draft an invoice, send it, track overdue ones, or prove payment with a receipt. Line items got retyped every time.
02
The story
If you cannot bill inside the product where you already track money, the product is only half useful. Invoices needed a clear life: drafted, sent, paid, or overdue. The catalog exists so people stop rewriting the same product lines on every bill.
03
What changed
Merchants create invoices, preview them, email them, and follow activity over time. When payment lands, a receipt links back to that invoice. If a receipt was a mistake, it can be voided. Catalog items fill invoice lines so names and prices stay consistent.
04
How it was built
Billing was designed as a full loop inside FloatMerchant: create, send, get paid, prove it. The catalog sits underneath so the boring part (the same items and prices) stays reusable. The point was to keep the money story in one product instead of forcing a side tool for invoices.
05
Outcome
- Merchants can bill without jumping to another tool for the basic job.
- Receipts prove payment when money arrives.
- The catalog stops copy-paste line items.