How we arrive at a delivery date. This is the calendar we work in.

Anyone can put "48 hours" on a website. The question is what happens in the week it is not true. Here is the part of the studio that answers that, and the reason a date is never offered before it has been checked — and never as a promise we have not reserved the day for.

Start an order See a delivered order

VISUAILS Studio Example with made-up data

VIS-2608-4471 · VOLT

20 products · catalog and lifestyle

  1. Received
  2. In production
  3. Checked
  4. Delivered
Your delivery week 10 – 11 Aug fixed before you paid

The first images are in

2 waiting for your approval · 1 back for revision

  • Product 1 · front Approved
  • Product 1 · back Waiting for you
  • Product 2 · front Revision
  • Product 2 · detail Waiting for you
Open and approve Download everything

All 140 images of this order arrive the same way — 7 per product. You approve them one at a time and the rest of the delivery keeps moving.

We check the calendar before we offer you a date.

The date picker on the order form does not show a list of dates. It asks the calendar what the studio has actually committed to on those days, removes every window the studio cannot hold, and offers the first one it can.

The four rules the planning runs on
  • Counted in products, not ordersA studio day holds 14 products, and a reserved window is 2 days. One order of thirty products asks for fifteen on each of those two days — not "thirty somewhere in there".
  • One ceiling, one placeThe limit is a single configurable number, and 3 of every 14 stay off it so a small order still runs in a normal turnaround. There is no second rule anywhere that can quietly disagree.
  • Size decides, at 10 productsFrom 10 products an order goes into the calendar and holds a committed date. Smaller orders run in a normal turnaround and yield to it, which is what makes the committed date committed.
  • Nothing is promised twiceA window that has been offered and taken is gone from the picker before the next person sees it.
VISUAILS Studio side Example with made-up data

What the date picker asks

14 products per studio day, 3 of which stay free for small orders. A window is 2 open days.

The request VIS-2608-4471 · VOLT · 20 products
  • Mon 3 Aug 8 / 11 Too soon
  • Tue 4 Aug 11 / 11 Too soon
  • Wed 5 Aug 11 / 11 Too soon
  • Thu 6 Aug 6 / 11 Room
  • Fri 7 Aug 2 / 11 Room
  • Sat 8 Aug 0 / 11 Room
  • Sun 9 Aug 0 / 11 Room
  • Mon 10 Aug 0 / 11 Window
  • Tue 11 Aug 0 / 11 Window
  • Wed 12 Aug 11 / 11 Full
  • Thu 13 Aug 0 / 11 Room
  • Fri 14 Aug 0 / 11 Room

The last 3 of every day cannot be booked as a window. They stay for orders running in the normal turnaround. The first 2 days are not production time: the products have to arrive and be looked at before a date means anything.

Offered 10 – 11 Aug

20 products ask for 10 on each day of the window, so it needs two days that are completely free. Thursday and Friday have room, but not enough — so that window is not offered.

Same calendar, smaller order 8 products · 6 – 7 Aug

This is why it is counted in products and not in orders: the answer depends on what has to be made, not on how many rows are in the table.

If nothing fits inside the horizon, you get no date. There is deliberately no "closest we can do", because that is the date that has to be moved later.

One table, every order.

Our side of it is deliberately boring: a list of orders, the state each one is in, and the calendar the picker reads from. There is no dashboard of graphs, because a graph has never told anyone which order is late.

What sits in that table
Every order, one row
Reference, brand, product count, the window it holds and the state it is in.
Revisions come to the top
A revision request from a client portal lands in its own list, with the note the client wrote, in their words.
A state change writes both sides
Moving an order writes the studio record and the client-visible timeline in the same move — which is why the portal is never out of date with the studio.
VISUAILS Studio side Example with made-up data

Revision requests

1 open

VIS-2608-4462 · Studio Halte Product 3 · back came in today 13:58

The back is turned slightly, which makes the logo sit crooked.

Take it onOpen the image

The note is here as the client wrote it. Nothing is summarised and nothing is turned into a category.

Orders

ReferenceBrandProductsWindowStatus
VIS-2608-4471 VOLT 20 10 – 11 Aug In production
VIS-2608-4468 Nord Label 12 3 – 4 Aug Being checked
VIS-2608-4462 Studio Halte 8 4 – 5 Aug Revision
VIS-2607-9920 Kade 4 4 Awaiting payment

Every order sits on the same list, in the same table. There is no separate row for big accounts.

One write

We set it

Delivered Revision

today 13:58

VISUAILS Studio shows

Revision asked · product 3 · back

today 13:58

The same time twice, because it was not written twice. The status change and the timeline the client sees are the same write — which is why the portal cannot fall behind.

The last step is a person.

Nothing is auto-delivered. Every visual in every order is looked at before it goes out, and the looking is a state the order has to pass through rather than a claim on a page.

The log records that review. Every approval and every revision is saved with a date against the image it belongs to. The same record you use to approve the order is the one we can read back to you months later.

Read the AI Act page

Photo to come

Work back from your launch date.

From 10 products we take that week out of the calendar for your order. That is why we can put the date in writing, and why a week that is full is offered as full.

  1. 01 Your launch date The day the collection has to be live. Everything else is counted backwards from here.
  2. 02 Your reserved date The delivery date we hold, on orders of 10 products or more. Once the calendar has cleared it, nothing in the studio may push it. We aim to deliver inside 48 hours of that date, and usually do. That part is what we work towards, not what we promise. Below that count an order runs in the normal turnaround.
  3. 03 Minus one folder The day you send the photos. That is your part finished, and the date is already locked.

Weeks are booked one at a time, and a full week is offered as full rather than as a longer wait.

See which weeks are open

What this does not do.

Worth saying plainly, because a page about a mechanism that only lists what works is a brochure.

  • It does not guarantee a window it has not clearedIf the calendar is full, you are offered the next window that is not. You will not be told yes and then rescheduled.
  • It does not rush an order past the reviewThe reserved delivery date is the date the work fits in, not a target the studio sprints at. An order that is not right does not ship on time; it ships right.
  • It does not scale by hiringThe ceiling is a real number and it stays a real number. When the studio is full it says so, which is the only version of this that is worth anything.

Book a window the calendar has cleared.

The date you are offered is one the studio has already checked it can keep.

Start an order See it on your own product first

Cookie preferences

Necessary cookies keep you signed in and remember this choice. They cannot be switched off, and they are all the site sets today.

Necessary

Sign-in sessions for VISUAILS Studio and for the admin side, and this preference itself. Always on.

Always on

Anonymous, cookieless page counts so we can see which pages are read. Off unless you turn it on, and nothing loads until you do.