> For the complete documentation index, see [llms.txt](https://help.pixfizz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pixfizz.com/faqs-and-troubleshooting/shopper-faqs.md).

# Shopper FAQs

<details>

<summary>How can I make shipping unavailable for certain products?</summary>

TBC

</details>

<details>

<summary>How can I make certain products unavailable for pickup, ship-only?</summary>

</details>

<details>

<summary>If I add my own CSS, do I lose the template's styles?</summary>

No. Your custom CSS is **appended** to the template's stylesheet, not swapped in place of it. Everything the managed template provides is still loaded, and your rules come after it.

Two things follow from that:

* You never need to copy the template's CSS into your own file to keep it. Add only what you are changing.
* Because your rules come last, a rule of equal specificity will win. If something still does not apply, the template's rule is more specific, and you can either match its specificity or use `!important`.

This also means improvements we make to the template's stylesheet continue to reach your store. Adding custom CSS does not freeze you on the version that was current when you added it.

</details>

<details>

<summary>If I override a snippet or a page, do I still get template updates for it?</summary>

No, and this is the important difference from custom CSS.

An override of a **snippet** or a **page** *replaces* that file for your store. From that point on your store uses your copy and nothing else, so later improvements and fixes we publish to that snippet or page do not reach you.

That is often exactly what you want when you have deliberately customized something. It is a problem when the override was created long ago, nobody remembers why, and a feature appears not to work on your store while it works everywhere else.

If something behaves differently on your store than the documentation describes:

1. Check whether you have an override for the snippet or page involved.
2. If you do, compare it against the current template version.
3. Remove the override if you no longer need the customization, or re-apply your change on top of the current version.

| What you override   | What happens                                       |
| ------------------- | -------------------------------------------------- |
| Custom CSS          | Appended. You keep receiving template updates      |
| A snippet or a page | Replaced. You stop receiving updates for that file |

</details>

```
/site/shop/{{ collection.path }}
```

```
/site/product/{{ collection.path }}/{{ product.custom.url_path }}
```