For the complete documentation index, see llms.txt. This page is also available as Markdown.

Add custom CSS

Use the app's own style settings first, and add CSS in your theme only for the few things they don't cover.

The app's style settings cover most of what stores need. When they don't — a particular border radius, a tweak that should only apply on mobile — you can add CSS of your own.

Start with the built-in settings

Almost every appearance change people reach for CSS to make is already a setting in Quote settings > Customize. Check these before writing anything.

Where
What you can set

Button & widget > Style

Button type (Filled / Outline / Text link), Size (Medium / Large / Full width), Text color, Background color and Font size.

Quote form > Style

A style preset, plus Match theme styling if possible.

Quote form > Customize text

Font style.

Quote form > Customize form color

Title bar color, Title bar background, Color, Background color, Border color and Quote popup primary color.

Quote cart page > Enable Quote Cart Widget

Text color and Background color — these are the only two the floating widget takes.

The Style section of the Button and widget tab, showing Button type, Size, Text color, Background color and Font size
Most appearance changes are already settings — start here.

Match theme styling if possible does a lot of the work on its own: "Theme styling applies on your storefront and is not shown in this preview." Turn it on and look at your live storefront before deciding the form needs CSS. See Match your theme style.

Where to keep your CSS

Wherever you keep custom CSS, keep it somewhere you can find again and undo. CSS kept in your own theme has a useful side effect: it is versioned with the theme, so duplicating the theme before you edit gives you something to roll back to.

Work through the built-in settings above before you write anything. If you can't tell whether a change belongs in a setting or in CSS, ask support@samita.io first — it saves you maintaining a rule you never needed.

Finding what to target

Right-click the element on your storefront and choose Inspect. That shows you the class names to write rules against.

A storefront product page with the quote button below Add to cart, ready to be inspected in the browser
Inspect the quote button on your own storefront to find what to target.

Two things are worth knowing before you start:

  • The quote button renders with whatever Button text you set, in the place you picked under Button position — so check Product page button position before you go looking for it.

  • The floating quote widget, labelled Quote (n), sits in a container with the class grfq-quote-widget-container.

Can't find the button on a collection page to inspect it? Hover a product card. On modern themes the app attaches it to the theme's own quick-add control, so it sits at zero opacity until the card is hovered and then appears as a small icon rather than a labelled button. That is the theme's behaviour, not a missing style — see Quote button on collection pages.

A few practical rules

Rule
Why

Change one thing at a time

When something breaks you'll know which rule did it.

Test on mobile

Most quote requests come from phones, and a desktop-only tweak often breaks there.

Keep a copy elsewhere

Paste your CSS into a note as well, so you can restore it if needed.

Avoid !important where you can

It wins today and makes every future change harder.

Comment every rule

In six months, an unexplained block of CSS is something nobody dares delete.

After a theme change

Start with the app embed on the new theme. It is enabled in your theme, and until it is enabled nothing the app does appears on your storefront — see Enable the app in your theme.

Then check your CSS. It is written against your theme's markup, so after a theme switch or a major theme update, look at your quote button, quote form and floating widget — rules may need adjusting.

Next steps

Last updated

Was this helpful?