> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/avante-themes/sections/collections/new-arrivals-tabs.md).

# New arrivals tabs

Show the newest products from several collections in Avante, one tab per collection, sorted by creation date.

New arrivals tabs answers the one question repeat visitors have: *what is new since last time?* Each tab is a collection, and each tab shows that collection's most recent products first. One section covers several categories, so regulars can check their own corner without leaving the home page.

### How to add

{% stepper %}
{% step %}

#### Add the section

In the theme editor click **Add section**, then pick **New arrivals tabs**.
{% endstep %}

{% step %}

#### Add one Collection block per tab

Each **Collection** block is one tab. You can add up to **5**.
{% endstep %}

{% step %}

#### Name the tabs

Fill **Custom tab heading**, or leave it empty to use the collection's own title.
{% endstep %}

{% step %}

#### Set the media and the count

Each block carries its own **Custom image** or **Video**, and its own **Products** count — 3 to 50, 12 by default.
{% endstep %}
{% endstepper %}

### Good to know

**Each tab is one collection, not the whole store.** The section never scans your catalogue — it sorts the collection picked in that block and takes the first few products. To cover everything, point a block at a collection that contains everything.

**Newest means the product's creation date in Shopify.** Not the date you published it, and not the date it joined the collection. Re-creating a product — a re-import, or a duplicate made to fix something — gives it a fresh creation date and jumps it to the front of the tab.

**Each tab can carry its own media.** Exactly as in [Featured collection tabs](https://staylime.com/docs/avante-themes/sections/collections/featured-collection-tabs.md), the block holds a **Custom image** and a **Video**, with **Enable pause control**, **Enable mute control** and a position for those controls. Video is muted on load so that autoplay is allowed, and the controls appear only once a video is uploaded. Whether the media shows at all is the section-level **Collection image** setting.

**Products is a hard count, and there is no pagination.** 3 to 50, 12 by default. The tab shows that many products and stops. If you want shoppers to carry on browsing, fill **Button label** in the block so the tab links onward to the collection.

**Tab labels fall back twice.** Custom tab heading → collection title → placeholder text, so delete any block you are not using.

### Customization ideas

* Point each block at an automated collection built on a tag such as `new`, and the tabs keep themselves current.
* Keep **Products** at a multiple of your grid width so the last row is full rather than ragged.
* Put a video on the first tab only, so the section opens with motion and the rest stays calm.
* Use **Custom tab heading** for short labels — "New in" reads better on a tab than the collection's full name.

***

### Related

* [New arrivals collection](https://staylime.com/docs/avante-themes/sections/collections/new-arrivals-collection.md)
* [Featured collection tabs](https://staylime.com/docs/avante-themes/sections/collections/featured-collection-tabs.md)
* [Collections](https://staylime.com/docs/avante-themes/sections/collections.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://staylime.com/docs/avante-themes/sections/collections/new-arrivals-tabs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
