Keep Your Shopify New Arrivals Collection Always Fresh
Most "New Arrivals" collections are a lie. Products from months ago sit right alongside this week's releases because nobody remembered to remove them. Here's a two-workflow system that keeps the collection honest — automatically.
The problem with manual New Arrivals management
Keeping a New Arrivals collection accurate requires two actions for every product: add it when it launches, remove it when it's no longer new. In practice, the adding happens (sometimes) and the removing almost never does. The result is a collection that becomes meaningless over time.
The fix is to automate both actions with date-based triggers. DateCue does exactly this using a launch date metafield on each product.
How the system works
The whole thing runs on one metafield: custom.launch_date. Two DateCue workflows watch that metafield:
- Workflow 1: When the launch date arrives → add tag "new-arrival"
- Workflow 2: 30 days after the launch date → remove tag "new-arrival"
Shopify's smart collection rule picks up any product tagged "new-arrival" and drops products that lose the tag. Your collection is always accurate, always current.
Step 1: Create the metafield
Go to Settings → Custom data → Products and create:
- Namespace and key:
custom.launch_date - Type: Date or Date and time
Set this on every product you want to rotate through New Arrivals.
Step 2: Create the smart collection
Go to Products → Collections → Create collection. Set it to Automated and add the rule: Product tag → is equal to → new-arrival. Save. This collection will self-populate as products get the tag.
Step 3: The two DateCue workflows
Workflow 1 — Add the tag on launch:
Timing: On the date
Action: Add tag → new-arrival
Workflow 2 — Remove the tag 30 days later:
Timing: 30 days after the date
Action: Remove tag → new-arrival
Once both workflows are live, you never touch the New Arrivals collection again. Products flow in on launch day and out 30 days later, all without any manual intervention.
Tuning the freshness window
30 days is a good default but adjust it for your store's release cadence. A store that launches new products weekly might use 14 days. A store with less frequent drops might use 60 days. Change the offset on Workflow 2 to match what "new" means for your customers.
💡 Works alongside manual product status: DateCue only manages the tag — it doesn't change product status. If a product is still in draft on its launch date, it gets the tag but won't appear in any customer-facing collection until you make it active. Combine this workflow with a publish-on-launch-date workflow to handle both automatically.
Frequently asked questions
What if I have existing products that should be in New Arrivals?
Set their custom.launch_date metafield to a date in the past within your freshness window. For example, if your window is 30 days and a product launched 10 days ago, set the date to 10 days ago. DateCue will see the date has passed the "on the date" trigger and has not yet passed the "30 days after" trigger, so it'll add the tag on the next sync.
Can both workflows use the same metafield?
Yes — that's the design. One metafield, two workflows, different timing offsets. DateCue evaluates each workflow independently, so the add workflow fires on day 0 and the remove workflow fires on day 30 from the same date value.
What happens to products launched before I set up this system?
Products without the custom.launch_date metafield set are ignored by both workflows. They won't be touched. To bring existing products into the system, set the metafield on them retroactively.
Does this work with manual collections?
No — manual collections don't respond to tag changes automatically. You need an automated (smart) collection with a tag rule for this to work hands-free. If you currently use a manual collection, you can convert it or create a new automated one alongside it.
Ready to set this up?
DateCue runs both workflows automatically, checking every minute.
Start your free trial14-day free trial. No credit card required.