A faster path from your systems to your first working plan.
Setup is one wizard in three phases. Tightly fetches seven sets of your operating data in order, shows you what came in before anything plans against it, and saves where you got to so you can leave and come back.
| Category | Plan | ML forecast | Var | |
|---|---|---|---|---|
| Outerwear | $3.20m | $3.39m | +6% | $612k |
| Knitwear | $2.40m | $2.61m | +9% | $498k |
| Denim | $1.80m | $1.74m | −3% | $204k |
| Dresses | $1.40m | $1.37m | −2% | $0k |
| Accessories | $0.90m | $0.88m | −2% | $72k |
Dresses settled to −2%. $180k of OTB released to Knitwear.What breaks between signing and a plan you can work.
An import is a spinner
Something is happening to your data and nobody can say what. There is no per-set state to look at, so the only honest answer to where are we is that we are waiting.
A failure becomes a support ticket
Something did not land, the message is generic, and the clock stops while a human triages it. The team implementing has to chase the people fixing it.
You cannot leave and come back
Setup is a session rather than a record. Close the tab, lose the place, and the person who started it is the only one who knows what was answered.
The data is planned against before anyone checks it
Channels you do not sell on get forecast. Warehouses that hold nothing get replenished. Suppliers arrive with no lead time and quietly inherit a default nobody chose.
Three phases from your systems to a rhythm every order is planned against.
Tightly · onboarding· three stages from data to decisionLiveConnect, and watch seven sets land
Tightly fetches your warehouses and connections, channels, products and variants, inventory counts, suppliers and sales orders, in that order. Each carries its own state, and a failure carries the reason your system gave.
Review what came in, before it plans
Four sections, each with its own save: which channels Tightly plans for, which suppliers still use your default lead time, which warehouses hold sellable stock, and which warehouses each channel ships from.
Finish, and the rhythm is set
Your planning cadence and default lead time become the rhythm every order is planned against until a supplier or a policy says otherwise. The fiscal year you set decides which weeks a season holds.
SetupConnect→Review→FinishYour Tightly contact: JoshA set that fails carries the reason the connection served, and Tightly’s own staff channel is told without you raising a ticket.
8 channels, 34 suppliers and 6 warehouses came in from Shopify.
Where you stop is where you resume, section by section. Review cannot open until the first pass lands, because everything after it plans against what Review confirms.
Aurelia Studio plans weekly against a 21-day lead time.
What changes once setup is a record, not a project.
Seven sets, fetched in a fixed order
Warehouses and connections, sales channels, products and variants, inventory counts, suppliers, sales orders, then finalizing. Each one reads Not started, Syncing, Synced or Failed, so the state of your import is a fact rather than a spinner.
A failure that does not become a ticket
A set that fails carries the reason your connection served, and the failure posts to Tightly's own staff channel with your organisation, the set and the sentence. The connector gets fixed without you raising anything.
Resumable, section by section
Stop at any step. Tightly saves where you got to and brings you back to it, and Review saves each of its four sections on its own rather than making you finish all of them.
Nothing plans against unconfirmed data
Review cannot open until the first pass lands, because every page after it plans against what Review confirms. A channel you leave off is never forecast; a warehouse that does not hold sellable stock is never replenished.
Meet Ask Tightly, during setup
Every card carries the panel, with the step you are on and its served sentence already in hand. It answers what a set needs, and it does not do the extraction for you.
Meet the agentsRe-forecast ready: 3 categories have drifted from plan this week. Want me to stage the moves for your review?
The implementation you expect, and the setup Tightly runs.
One bar, and no way to name what stopped. The only route to an answer is a person, and the clock runs while they look.
“Import failed, can you take a look?”
Seven sets, each with its own state. The one that stopped carries the reason your system gave, and Tightly has already been told.
Your Shopify import stopped at Inventory counts.
Posted to Tightly with your organisation, the set and the sentence. No ticket raised.
Onboarding is one part of the connected plan.
Connect
Wholesale accounts declare their own conventions once, on the same principle.
Finance
Three numbers no order can supply are declared once, by an admin.
The connected plan
What Review confirms is what every capability afterwards plans against.
Who does the data work?
Tightly brings your operating data in and proposes the mapping. Ask Tightly answers what a step needs and carries the served sentence for a set that failed. It is honest about the boundary: it helps you review and configure, it does not do the extraction for you.
What happens when an import fails?
The set that stopped is named, with the reason your connection served rather than a diagnosis. The failure posts to Tightly's staff channel with your organisation, the set and the sentence, so the connector gets fixed without a ticket. On a self-serve install nobody will call you.
Can we stop halfway?
Yes. Setup saves where you got to and brings you back to it, and Review saves each of its four sections separately. A step the wizard skips is absent rather than greyed out, so the path you are on is the path you see.
What do we have to decide?
Five answers on one card: your name as it should read on a purchase order, your vertical, your currency, the month your fiscal year opens, and how often you plan. Then a default lead time and a replenishment frequency at the end. All of them are changeable later in Settings.
How long does it take?
That depends on your systems and the scope you agree, so we will not put a number on this page that we have not measured for you. Book a walkthrough and we will scope it against what you actually run.
See where you are, always. From your systems to a plan you can work.
There's nothing to rip out. Tightly runs on your existing ERP, EDI, e-commerce and POS. Give us 30 minutes and we'll walk you through it.