Software · Changed when you ask

Ask for a feature

If your account needs the warehouse to do something it does not do yet, that is a conversation rather than a refusal. It is our software.

01
A yes, or a straight no
02
Built on your real orders
03
No per-feature licensing
04
Tested on this floor first
What it produces

Ask for a feature, as you see it.

Requests come in through the same thread you use for anything else, and get a straight answer. Sometimes that answer is no — with the reason, and whatever we can do instead.

Requests from your accountLast 90 days
FR-02192 OctShipped 6 Oct

Our buyer wants packing lists per carton in their template, not yours.

CC

That is a day's work. Send us their template and we will do it.

FR-02249 OctDeclined, with an alternative

Can the floor hold returns back until our CS team has looked at them?

CC

No. Stock sitting unprocessed is how backlogs start, and it would only work if every packer remembered a special case. We will flag them to you instead.

A straight answer either way — a vague yes is worth less than a no
How it runs

Three steps, in order.

  1. Tell us what the problem isUsually more useful than telling us what the feature is — the underlying problem often has a simpler answer than the one you had in mind.
  2. We tell you honestlyWhether it is a day, a month, or something we are not going to build. A straight no is more useful than a vague yes.
  3. Built against your real workDeveloped and tested on your actual orders here, not demonstrated on sample data.
What that includes

What that includes.

  • Integrations with your channels and systems
  • Rules specific to how your orders work
  • Reporting cuts you need and we do not have
  • Retailer and marketplace requirements
  • No per-feature licensing to negotiate
What we need from you
  • The problem, rather than the feature — the underlying issue often has a simpler answer
  • A real example we can build against
What you get back
  • Integrations with your channels and systems
  • Rules specific to how your orders work
  • Reporting cuts we do not have yet
  • Retailer and marketplace requirements
  • A straight no where we are not going to build it
The honest bit

We will say no to things. Anything that would make the system worse for every other client, or that only works if the floor remembers a special case, is not worth building — and we would rather say so than build it badly.

Talk to someone who runs the floor

Want to see it on your own orders?

Run a four-week trial. No contract, no minimum — long enough that the returns from week one come back inside it.