Skip to content
Interface language: English
Imperium / Signal

Batch orders: customers should know which run their work has made

How to close shared production runs: material approval, late corrections, split sets and exceptions that actually make it into the schedule.

Article language: English

A dark glass vessel with a gold-toned lid stands near an open door. Inside is a pale fragment with a golden line.
In this article

At 12:07 a customer sends a message: “We approve it, with one small change.” The team closed the set for production seven minutes earlier. Someone must now decide whether to reopen it, remove one item or move the correction to the next run. The word “small” does not make that decision. It does, however, do a good job of pretending the decision has already been made.

Imagine a studio that prepares labels for a stationery collection. Every Tuesday it gathers approved materials from several clients and sends a combined set for production. One company orders six variants. Five are ready in the morning; the colour name of the sixth is still being discussed. The client believes the order made the deadline. The studio sees an incomplete set.

The problem lies at the boundary between runs. Even with few tasks and a team member available, someone must establish which version of which order will enter the next production run. A limit on work in progress (in Polish) will not answer that question on its own. A shared answer is needed: what exactly must be ready at the closing time?

An order in the inbox, material in the run

First separate two events that are easily blended in a sales conversation. Accepting a request means the company will attend to it. Including it in a run means that specified material has met the conditions for starting a particular cycle. Between the two there may be a data check, preparation of a proof and customer approval.

Printful Enterprise documentation, updated on 9 September 2026, says approval settings determine when imported orders are submitted for production. One option is submission at a set daily time in the configured time zone. An order retains the rule active when it was created. That is how Printful Enterprise describes order approval.

When setting your own cycle, ask whether a rule changed for next week will also apply to orders already accepted. If the studio moves its closing time from noon to ten, it should separately decide what happens to materials for which the old window was promised. Changing a time in a tool does not settle the conversation with those customers.

The acknowledgement should state the nearest run the material may enter and the condition for inclusion. “We have the files” and “the approved complete set will enter Tuesday's run” communicate different things. A similar distinction applies to response time and resolution time (in Polish): the first contact should not quietly become a promise that the work is finished.

At noon it must be approved, not merely sent

Jukebox describes a 2:00 p.m. Eastern Time approval cutoff for its stickers. If the customer orders a digital PDF proof for approval, that proof must also be approved before the stated time. The company recommends sending files earlier to allow time to prepare and review the proof. Jukebox's own instructions therefore distinguish supplying material from authorising its production.

The studio in our example can choose different hours, but it needs an equally clear final event. “Approval by Tuesday” leaves the time of day open. “Files by Tuesday, 12:00 Warsaw time” still does not say whether this means sending a first version or approving the result. Establish what the deadline means before shortening the wording for a form.

For the six-label order, the studio could adopt a completeness rule: all variants must be approved for the whole set to enter the run. The fifth approval would not start production of five variants if the offer covers one indivisible set. The customer should know about this dependency before Tuesday morning, especially when different people approve different variants.

Splitting can also be allowed. Five ready materials enter the nearest run and the sixth enters the next. That makes sense if the studio can actually accept, produce and deliver the order in parts. It also requires a clear answer about whether the customer will receive two deliveries and who approves the arrangement. The rule should reflect the work, not merely the convenience of a checkbox.

What remains after a batch closes

After the Tuesday cutoff, the team needs an identifiable set to work from. A simple record is enough: a run identifier, the orders it contains and the approved versions of the materials. A later customer message should not silently replace a file in a set already handed over. Otherwise two people may diligently produce two different versions of the same job.

At 11:40 the customer approves the green variant, labelled G-3 by the studio. At 12:00 the run closes with that version. At 12:07 a request arrives to change the name from “green” to “forest green”. The agreed rule may send that change to the next run. The confirmation should then name both states: G-3 remains in the current production run, and a new version will be prepared for the next approval.

If the customer wants to withdraw the current variant, check whether that is still possible at the stage the work has reached. It is not enough to add “please stop” in a place the person doing the work does not monitor. The batch-closing agreement should specify how to make such a request and who will confirm whether the work was actually stopped.

This boundary appears in a separate Sticker Mule instruction: once all proofs are approved, an order automatically enters the production queue and rush service can no longer be added. The company says the option must be chosen earlier, during ordering. The rule shows a specific point at which subsequent work starts.

Aeneia conceptual photography

For your own service, similarly establish which decisions must be made before the set is handed over. This could include choosing combined or split production. Do not call every later request an ordinary correction if it changes an already agreed way of delivering the work. A larger change may need a separate agreement on the scope of a service project (in Polish).

When the studio itself used up the approval time

Consider another version of the order: the customer sent complete information on Monday morning, but the studio prepared the proof only at 11:55 on Tuesday. The window closes five minutes later. Formally the time is clear. Operationally the company has left the customer five minutes to check six variants. This should not be treated in the same way as an answer sent a full day after a finished proof was available.

In its description of proof approval time, Sticker Mule separately says that the customer is not penalised for delays caused by the company in preparing the proof. After all materials are approved, the company sends an estimated delivery date. This is a narrow element of that service's own rules, useful as an example of separating the causes of delay.

The studio should therefore set its own time for making material ready for review. If it misses that point, it needs a specific decision: an agreed exception, another run or a different deadline for the whole order. An automatic “not approved on time” message alone obscures where the delay actually arose. Keep both dates or times: when the correct version was made available and when approval was received.

If the tools cannot reconstruct this sequence, examining information flows and automation opportunities with Aeneia Audit may help. Messages, file versions and the way they are assigned to runs can be a starting point. First establish what it means for material to be ready, so that an automated reminder does not ask a customer to approve a proof they have not yet received.

A run calendar also needs a delivery date

The cutoff may be clear while the customer still does not know when they will receive the materials. Closing a set on Tuesday is not the same as delivering it on Tuesday. The studio should connect the run name with the subsequently agreed deadline. In the six-label order confirmation, the customer can then see the approval time and the expected delivery of finished work separately.

A week in which the usual closing day falls on a day the studio treats as a holiday needs a specific decision. Does the run move by a day, or is it skipped and the orders moved to the next one? If the company simply omits Tuesday from the calendar, a customer may submit a correction on Monday believing the familiar rule still applies. Publication of the changed window should also reach people with materials still open.

In our set, five approved variants may wait for the sixth for more than one cycle. Establish whether earlier approvals remain valid if the customer changes the collection's shared name in the meantime. That event may require approval of the whole set again. Identify it before assigning the order to the next batch instead of relying on old approvals for content that is no longer current.

The team's available capacity is another boundary. “Materials approved before noon may enter the run” does not automatically mean the studio can accept any number of sets. If it confirms a place separately, it should do so before asking for final approval. The customer then knows whether they are closing material for an already agreed production slot or merely declaring readiness for a date to be arranged.

Test the rule with two orders approved at 11:50. The first has a previously confirmed place; the second appeared for the first time that morning. If both automatically receive the same promise even though the team can complete only one, the intake window is hiding a capacity problem. The solution is explicit confirmation of assignment to the run, visible to the customer and the person doing the work.

An exception must enter the calendar, not just the conversation

The studio will accept some late changes. Problems begin when a salesperson confirms an exception to the customer while the person doing the work still has the original list. There are then two schedules: an official one and an oral one, usually stored in someone's memory. Memory has many advantages, but it is hard to send it a version number for a colleague on leave.

An exception needs approval from someone who knows the state of the current work. In our example that person may permit one item to be replaced before the set is passed on, or refuse if the change would reopen a closed stage. The decision should state whether only item G changes or whether the deadline for the other five variants changes too. The customer should not learn about that dependency at delivery.

If the extra work displaces another order, account for that effect as well. “We managed to add the label” sounds good until another customer's confirmed deadline slips without explanation. An honest deadline promise between sales and delivery (in Polish) requires the consequences to be visibly confirmed, especially in a shared cycle serving several customers.

Test the boundary on one ordinary Tuesday

Review one closed run and reconstruct the orders that changed batch. For each, establish which version was ready before the cutoff and exactly what happened afterward. Treat missing data, waiting for approval and a correction after earlier approval separately. Only then can you see whether the team is struggling with late responses or unclear conditions for inclusion.

During a supplier change in a transition period (in Polish), a similar boundary concerns the party doing the work. Here it concerns the next run. If the studio introduces both transitions at once, the confirmation should name both the provider and the cycle. “We have accepted it” then leaves particularly much room for two different interpretations.

Finally, ask someone outside the team to use the confirmation to say where the six labels will go if the final change arrives at 12:07. They should be able to identify a particular set rather than phone three people. If the answer requires a conversation, improve one rule before next Tuesday: what closes at noon and what happens to the material that arrives later.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear