This release is about momentum: helping independent software teams bring an existing business over, connect the tools they already trust, and grow with people who genuinely know their product.
Several of these projects have been moving behind the scenes for months. Together, they remove friction at three different moments—before launch, during an everyday workflow, and after a customer recommends you.
- Partner sales
- Guided migrations
- Workflow connectors
- Developer additions
- Quality improvements
- What is next
Partner sales are opening up
Teams can now invite advocates, choose a reward model, and see referred orders beside the rest of their storefront reporting. Partners get a focused portal with links, earnings, and payment status—without being dropped into a seller dashboard.
We designed the first version around clarity rather than campaign sprawl. One partner can understand what happened to every visit and order; one operator can reconcile every reward.
Partner workflow
A single trail from invitation to approved reward.
A migration path you can inspect
Moving a live store should not feel like putting revenue into a black box. The new importer groups products, customers, subscriptions, and license history into separate runs. Each row keeps its source identifier and displays anything that needs a decision.
For larger moves, our team can rehearse an import into a private workspace before the final transfer. That makes field mapping and edge cases visible while the old storefront is still running.
Automations that speak in useful events
The connector library now exposes the moments operators actually act on: a trial starts, a subscription pauses, an invoice needs attention, a license is activated, or a reward becomes payable.
Actions can create a customer, issue a license, add an order note, or update a partner. Every automation includes a delivery log and a replay control, so a temporary failure does not become a support mystery.
“The win was not adding another tool. It was finally knowing which event kicked off each handoff.”
Developer additions without ceremony
We added narrower endpoints for customer lookup, subscription changes, and reward records. Event payloads now share a predictable envelope, and test events can be generated without creating disposable transactions.
Small changes with a large combined effect
Release notes tend to give equal weight to changes that users do not experience equally. These are the refinements that showed up most often in support and session reviews.
Repeat buyers can reuse billing details without rebuilding the rest of the order.
Product, tax, discount, and renewal context now follow one consistent hierarchy.
Date ranges and status choices remain in place while operators move between views.
Pending, scheduled, and completed funds each explain what happens next.
Next: fewer tabs between idea and income
We are testing a calmer home for launches: the product, its audience, and its first distribution steps in one place. Early partners are also helping us tune multi-store payouts and partner tiers.
As always, release access will widen in steps. We would rather learn from real stores with real constraints than declare a system finished from a tidy demo.
Keep the signal coming
If a migration, connector, or partner workflow is slowing your launch, send us the exact handoff. The most useful product feedback describes the moment work stops—not only the feature someone hopes will solve it.