The Batch activity in GelatoConnect helps streamline production by grouping order items before they proceed to later stages like imposition and manufacturing. This activity can be configured to release batches based on time, count, or a combination of both. Additionally, you can control how items are grouped, sorted, and handled when reprints are involved. This article provides a complete walkthrough on setting up, customizing, and managing the Batch activity effectively to improve workflow performance.
Setting up the Batch activity
The Batch activity is available in the Activities panel of the workflow editor. It allows you to define how items should be grouped and when they should be released to the next step in the process.
Choosing how batches are released
You can configure batch release in three flexible ways:
By count
Define the number of order items needed before a batch is released. For example, a count of 10 means a batch will release once 10 individual items are grouped.Important: An item with quantity 50 still counts as one item. To count quantities instead of items, use the "context quantity" attribute if available.
Default count is 1, which would release items individually unless adjusted.
By time
Set specific weekdays and a time of day for automatic batch release. This is especially useful for aligning production with operator shifts, such as every weekday at midnight.By time or count (whichever comes first)
Select both time and count as release conditions. The batch will release when the first condition is met.
Grouping and organizing batch contents
Defining batch grouping rules
Use the Batch by field to control how items are grouped. This is useful for ensuring similar items are processed together. Grouping is based on attributes from the order’s context.
Common grouping attributes include:
Color type (e.g., 4/4 or 4/0)
Orientation (horizontal or vertical)
Product UID
Spine size
Client ID
Dispatch date
To group by multiple fields, separate them with a forward slash.
Example: dispatch_date/product_uid
Sorting within a batch
Control the processing order of items inside a batch:
Order by: Select a key attribute to sort items, such as order ID or dispatch date.
Sort: Choose ascending or descending order.
Note: Sorting is lexicographic, meaning it follows string-based logic unless otherwise specified.
Managing special cases and batch processing
Handling reprint orders
Enable the Reprint Batch Group toggle to manage reprints separately. When active:
Reprints are grouped into a distinct batch.
The same "Batch by" rules still apply.
This ensures that reprints don’t mix with new orders and are traceable through production.
Testing and monitoring batches
Once setup is complete:
Save and test the configuration to confirm it performs as expected.
Go to the Workflows section in GelatoConnect and open the Batches tab.
Here you can:
View all current batches and their progress.
See how many items are grouped and how many are remaining before release.
Manually release a batch if needed.
Access or modify configuration settings for future batches. Changes do not affect already-processed items.
Practical tips for better batching
Schedule time-based releases at the beginning of work shifts for smoother handoffs.
Use "Batch by" to separate incompatible items and reduce production errors.
When possible, test your workflow using real order data to fine-tune grouping and release conditions.
Keep sorting simple and consistent with production priorities like due date or dispatch date.
Frequently asked questions
Can I group by both product and client ID at the same time?
Yes. Use the forward slash format in the Batch by field: product_uid/client_id.
What happens if neither time nor count conditions are met?
Items remain in the batch until one of the conditions is satisfied or the batch is manually released.
Are quantities within items ever used for batching?
By default, batching uses item count, not quantity. Use the "context quantity" if available to batch by quantity.
Can I release items individually?
Yes. Set the count to 1 and leave time-based release disabled.
Will changing batch settings affect items already batched?
No. Changes apply only to future batches.
Next Step: 🔗[Getting Started - GCW] Setting Up SLAs
📝 Not what you needed?
Help us improve this article, send us an email to [email protected] — please include the article title.