01Do I need to set anything up before using Structa?+
No. The app reads every metaobject definition in your store the
moment it boots. If you've already modeled things in Shopify,
they'll be in the sidebar the first time you open Structa.
02Which field types are supported?+
42 of Shopify's 52 field types — text (single, multi-line, rich
text), integer, decimal, date, date & time, boolean, color,
rating, money, link, URL, ID, JSON, weight/volume/dimension, all
reference types (product, variant, collection, customer, page,
file, metaobject, mixed, taxonomy), choice lists, and list
variants of each. The remaining 10 (article reference, company
reference, and a few list types) show read-only and edit through
the Shopify admin.
03How does saving many edits at once work?+
One ⌘S (or Ctrl+S on Windows/Linux), one submit. Structa sends
every edited row together — there's no per-save row cap. Rows
that fail validation stay in the editor marked as still-edited so
you can fix them and retry; successful rows commit immediately so
you never lose work.
04What's the AI / MCP integration?+
MCP (Model Context Protocol) lets you point Claude — or any
MCP-aware agent — at Structa using a scoped token (30, 90, or
365-day expiry). The agent can read your data and propose
changes; it has no path to write directly. Proposals land in the
Review Queue with side-by-side diffs and bulk approve/reject.
Tokens are stored as SHA-256 hashes and can be revoked instantly.
05Is my data safe?+
Yes. Structa is GDPR and CCPA compliant. No changes are applied
without explicit action; agent proposals always require manual
approval; tokens are scoped and revokable instantly.
06How big can an export or import be?+
CSV export covers what's on screen, up to the 5,000-row table
view and respecting active filters. CSV import handles 250 rows
and 5 MB per file; rows with a handle upsert (update if present,
create if not), rows without one create new with an
auto-generated handle. JSON exports for definitions have no row
cap (schema only).
07Can I copy a definition to another store?+
Two ways. Export the definition as JSON in store A and import it
into store B — or generate a share token in store A and paste it
into store B's import flow to pull the definition live, no file
involved. Either path moves the structure (fields, validations,
settings); entries move separately via CSV if you want them too.
08Can I cancel?+
Any time, from the Plans page inside the app. Your store falls
back to the free tier (3 definitions, 5 entries each); your
metaobjects and data all stay in Shopify. Billing is handled
through your Shopify account.