Importing your Square or Stripe catalogue — StudioOps Help

If you're moving to StudioOps from a system where you already entered your services (Square Catalog, Stripe Products, anywhere), you don't have to retype them. StudioOps reads your existing catalogue on first connect and lets you bring it across in one tick-and-confirm pass.

The same flow works for both providers. It runs once when you first connect, and you can re-run it any time from Settings → Services.

1. When the import appears

The first time you connect Square or Stripe to StudioOps, the dashboard checks two things:

Are you connected to that provider?
Do you have three or fewer StudioOps services?

If both are true, a banner appears on your dashboard the next time you load it:

Bring your Square menu across in one click Import your existing Square catalogue · Not now

(Same shape for Stripe — "Bring your Stripe Products across".)

If you skip with Not now, the banner doesn't reappear. You can still trigger the import any time from Settings → Services → Re-import from Square (or Stripe).

The banner is suppressed once your StudioOps service count goes above three — by then you've clearly typed services in manually and a one-click overwrite would be confusing.

2. The preview screen

Clicking Import from Square (or Stripe) opens a preview screen. StudioOps reads your existing catalogue and shows every item it found in a table:

✓	Service	Duration	Price	Payment	Deposit

For each row you can:

Tick / untick to include or exclude from the import.
Edit the name — useful if your Square names are abbreviated (e.g. "GM Classic" → "Gel manicure — classic").
Set the duration in minutes. Square and Stripe don't carry duration natively, so the import defaults each row to 30 minutes — you confirm the right number before submitting.
Edit the price. Pre-filled from the source system. Edit if needed.
Set the payment rule. Three options: No card (booking confirms instantly), Deposit (customer pays a deposit at booking), Full at booking (full price up front). Defaults to "No card" — pick what fits your service.
Set the deposit amount. Only enabled when the payment rule is Deposit.

Below the table, a "Select all" / "Select none" pair lets you bulk-toggle.

When you're ready, click Import N services.

3. What happens on submit

StudioOps validates every selected row (deposit can't be more than the price, deposit row needs a deposit amount, every row needs a duration above zero) and then writes them into your StudioOps services list.

Each imported row gets an audit-log entry so you have a record of what came from where + when.

You're bounced back to Settings → Services with a "Imported N services, updated M" confirmation. The new services are immediately bookable on your public booking page.

4. Re-importing later

If you add services to Square or Stripe after the first import, you can re-run the import at any time:

Settings → Services → Re-import from Square (or Stripe).

The preview shows every item from your source catalogue. Rows that were imported before are flagged with Already imported — submitting will UPDATE the existing service and start unticked (so a re-import-by-mistake doesn't bulldoze your edits). New rows start ticked.

This means re-import is safe to run as often as you like. Nothing gets duplicated.

If you've changed the name, duration, or price of an already-imported service inside StudioOps and you tick its row on re-import, your StudioOps edits get overwritten by the source values. So: only tick already-imported rows when you want to pull fresh data from the source.

5. Things StudioOps deliberately skips

Square: multi-variation items

If a Square item has more than one variation (e.g. "Haircut" with "Short hair / Long hair / Curly" variations), StudioOps skips it during the preview and surfaces it separately in an amber section:

1 item needs manual attention Haircut — 3 variations

The reason: StudioOps mirrors edits back to Square via a one-way push. If we imported each variation as a separate StudioOps service, editing one would corrupt the others on Square. Until we ship a richer integration, multi-variation items stay in Square — manage them there or split them into separate Square items first.

If you want each variation as its own bookable StudioOps service, the workaround is to split them in Square (create "Haircut — Short", "Haircut — Long", "Haircut — Curly" as separate items), then re-import.

Stripe: non-GBP / recurring / custom-amount Prices

StudioOps skips Stripe Prices that are:

Not in GBP — v1 is GBP-only. Other currencies stay in Stripe; they appear in the amber skipped section with the currency code for clarity.
Recurring (subscription Prices) — StudioOps services are one-off bookings, not subscriptions. Stripe Subscriptions live in your Stripe Billing dashboard, not in a booking tool.
Custom-amount or tiered — Prices without a fixed unit_amount (pay-what-you-want, volume-tiered, etc.) need a fixed price to render on a booking page. Set a fixed amount in Stripe and re-import.
On an archived Product — Stripe Products marked inactive are excluded.

Each skipped row tells you exactly why so you can fix the source if you want it imported.

6. After the import

Three quick things to check:

Visit your public booking page (studioops.uk/your-slug/book) and confirm the imported services render the way you expect. If a description was missing from the source, the row imported with no description — go into Settings → Services and add one if you want it on the booking page.
Tick which staff can deliver each service in Settings → Staff → person. The import doesn't try to guess which of your team can do what — that's a manual step per the Setting up your people article.
Confirm the payment rule on each service. If you imported as "No card" for everything but actually want a deposit on some services, edit those services and switch the rule.