Changelog
What shipped, and when
Every release since the first private build. Breaking changes are announced in the API version header, in the release notes, and by email to anyone still on a sunsetting version.
v1.0.0MajorCurrent28 August 2026CubieFlow 1.0
- Public launch. 27 modules across orders, inventory, money, messaging, growth and connections.
- Unified inbox covering website chat, Messenger, Instagram, TikTok, WhatsApp, SMS and email.
- Admin console with role-scoped access and an append-only, hash-chained audit log.
- Full light and dark themes, with dark built as its own palette rather than an inversion.
v0.9.4Feature14 August 2026Accounting integrations
- QuickBooks Online, Xero and Wave connections for ledger sync.
- Journal entries posted per payout, mapped to your chart of accounts.
- Per-channel tracking categories on Xero.
v0.9.2Feature31 July 2026Carrier connections, individually
- EasyPost and Shippo as aggregators; DHL Express, UPS and FedEx on your own account numbers.
- Rate shopping now respects weight bands and service caps.
- Customs documents generated for international shipments.
v0.9.0Improvement10 July 2026Navigation rebuilt around nav roles
- Screens now declare how you reach them — tab, filter, action or detail.
- Orders went from fourteen tabs to four; Settings from sixteen to nine.
- Promoted modules move out of their group rather than being duplicated into the top of the sidebar.
- Command palette indexes all 267 screens.
v0.8.6Feature19 June 2026Demand forecasting
- Reorder points calculated from sell-through, lead time variance and seasonality.
- Confidence bands widen where history is thin, rather than presenting a false precision.
- Purchase order suggestions grouped by supplier.
v0.8.1Fix22 May 2026Sync reliability
- Rate-limit quota now partitioned per workspace, so a bulk import cannot starve live order sync.
- Failed records retain their payload and the provider's own error message for replay.
- Nightly reconciliation pass compares counts against each provider and repairs drift.
Versioning
How we handle breaking changes
The API is versioned by date, pinned per key. A version is supported for at least twelve months after its successor ships, and nothing breaking ever lands inside an existing version.
Announced three ways
Release notes, a response header, and email to anyone still on a sunsetting version.
Twelve months minimum
You get at least a year from the day the next version ships before yours sunsets.
Contacted individually
At 90, 30 and 7 days, workspaces still on an old version hear from us directly.
Building against the API? Read the reference.
Ready to run your business in one flow?
Start a 14-day free trial. No credit card, no setup fee, and your data stays yours.