Store administration: the parts, in plain words

64 parts and 15 phrases. Apps in this area include Shopify admin, Shopify Flow, Mesa, Zapier, Make, Matrixify.

Staff and accessstore.staffShowWho can sign in to the admin and what each person may see and change.

Staff accountsstore.staff.accountShowThe people who work in the admin, how they join and how their access is paused or removed.

How to extend

EventMany side by sideevent.customer.createdStaff and customers share one user table, so a plugin that reacts to new accounts subscribes to the account event and checks the role.
SlotMany side by sideadmin.slot.settings.plugin_settingsA plugin adds its own panel, such as an HR or shift note, to the staff member's detail page.

Part	Litestore today	How to extend
Staff member`store.staff.account.staff_member`A staff member is a user with an admin role who signs in to the admin and acts under their own name.	Core`modules/team/admin`	Event · manySlot · many
Staff invitation`store.staff.account.invitation`A staff invitation emails a sign-up link with a chosen role, and the person becomes staff when they accept it.	Core`modules/team/admin/invitation-crud.ts`	Event · manySlot · many
Email sign-in link`store.staff.account.sign_in_link`An email sign-in link signs a staff member in with a one-time link sent to their address instead of a password.	Core`platform/auth/server.ts`	Event · manySlot · many
Two-step sign-in`store.staff.account.two_factor`Two-step sign-in asks for a second code from an app or phone after the first sign-in step.	Plugin	Event · manySlot · many
Account ban`store.staff.account.ban`An account ban blocks a user from signing in, with a reason and an optional end date, until it is lifted.	Core`modules/team/admin/ban-user-dialog.tsx`	Event · manySlot · many
Remove staff account`store.staff.account.remove`Removing a staff account deletes the user and their uploaded images, and refuses to remove your own account or anyone at manager rank or above.	Core`modules/team/archive-users.ts`	Event · manySlot · many
Sign in as a user`store.staff.account.impersonation`Signing in as a user opens the store as that customer or staff member for support, with a banner and a way back to your own account.	Core`ui/impersonation-block.tsx`	Event · manySlot · many

Roles and permissionsstore.staff.accessShowThe rules that set which admin areas and actions each staff member may use.

How to extend

Core onlyRoles and permission checks stay in core, because every admin action and API call runs through one permission check.

Part	Litestore today	How to extend
Staff role`store.staff.access.role`A staff role is a named bundle of permissions, such as owner, admin, manager, editor, support, marketing or analyst.	Core`platform/permissions/roles.ts`	Core only
Area permission`store.staff.access.permission`An area permission pairs an admin area with an action, such as orders:view or products:edit, and every admin action checks it before it runs.	Core`platform/permissions/check.ts`	Core only
Per-person permission change`store.staff.access.per_person_override`A per-person permission change grants or removes single permissions for one staff member on top of their role.	Core`modules/team/admin/permission-editor.tsx`	Core only
Custom role`store.staff.access.custom_role`A custom role is a role the merchant names and fills with permissions in the admin, beside the built-in roles.	Plugin	Core only
Seller access`store.staff.access.seller_scope`Seller access limits a marketplace seller to their own products, orders and earnings in a separate seller portal.	Core`platform/permissions/vendor.ts`	Core only

Store settingsstore.settingsShowThe few facts about the store that an owner sets once and changes rarely.

Store detailsstore.settings.detailsShowThe store's name, contact details, legal business facts and currency that appear on pages, emails and invoices.

How to extend

SlotMany side by sideadmin.slot.settings.plugin_settingsA plugin adds its own settings page under the admin settings menu.
Assistant toolMany side by sidegetStoreSnapshotThe assistant reads the store's settings and counts through the getStoreSnapshot tool.

Part	Litestore today	How to extend
Store name and logo`store.settings.details.store_identity`The store name, description, logo and favicon appear in the storefront header, browser tab and emails.	Core`modules/settings/admin/site/branding-form.tsx`	Slot · manyAssistant tool · many
Support contact`store.settings.details.contact`The support email, support link and social links tell customers where to reach the store.	Core`modules/settings/schema.ts`	Slot · manyAssistant tool · many
Business information`store.settings.details.business_info`Business information holds the legal name, address, phone number and tax id that appear on invoices and legal pages.	Core`modules/settings/schema.ts`	Slot · manyAssistant tool · many
Store currency`store.settings.details.currency`The store currency is the one currency every price, order and payout is recorded in.	Core`app/admin/settings/currency/page.tsx`	Slot · manyAssistant tool · many
Setup guide`store.settings.details.setup_guide`The setup guide lists the steps a new store completes before it can sell, such as adding a product, a shipping rate and payments, and checks each step against live data.	Core`modules/settings/setup-guide.ts`	Slot · manyAssistant tool · many
Store password page`store.settings.details.store_password`A store password page hides the storefront behind a password while the store is being built.	Plugin	Slot · manyAssistant tool · many

Day-to-day operatingstore.operateShowThe admin home, the queues of work waiting for staff, the alerts that reach them and the tools for acting on many records at once.

Admin home and queuesstore.operate.homeShowThe first screen staff see and the counts of work waiting for them.

How to extend

SlotMany side by sideadmin.slot.home.cardsA plugin adds a card to the admin home, such as a count from its own queue.
Assistant toolMany side by sidegetStoreSnapshotThe assistant reads the same queue counts as the sidebar badges through getStoreSnapshot.

Part	Litestore today	How to extend
Work queue count`store.operate.home.work_queue`A work queue count shows how many orders, returns, refunds, reviews, disputes and applications are waiting for staff, as badges in the admin menu.	Core`modules/operations/queue-counts.ts`	Slot · manyAssistant tool · many
Approval step`store.operate.home.approval`An approval step holds a record such as a creator or seller application as pending until staff approve or reject it, and records when.	Core`modules/operations/status.ts`	Slot · manyAssistant tool · many
Admin search`store.operate.home.admin_search`Admin search opens with a shortcut key and finds orders, customers, coupons, campaigns and messages by name, number or email, limited to the areas the staff member may see.	Core`modules/operations/admin/search-actions.ts`	Slot · manyAssistant tool · many
Staff note`store.operate.home.staff_note`A staff note is a private comment staff leave on a record, such as an order, that customers never see.	Core`ui/admin/staff-notes-card.tsx`	Slot · manyAssistant tool · many

Bulk actionsstore.operate.bulkShowActing on many selected records at once, and whether a removal can be undone.

How to extend

SlotMany side by sideadmin.slot.product.bulk_actionA plugin adds its own action to the bar that appears when rows are selected in an admin table.

Part	Litestore today	How to extend
Bulk action`store.operate.bulk.batch_action`A bulk action runs one change, such as delete, archive or approve, on every row selected in an admin table.	Core`ui/admin/tables/default-batch-bar.tsx`	Slot · many
Archive`store.operate.bulk.archive`Archiving hides a record from lists and the storefront but keeps it in the database so it can be restored.	Core`platform/crud/base-crud.ts`	Slot · many
Permanent delete`store.operate.bulk.permanent_delete`A permanent delete removes the record for good after staff confirm it in a dialog.	Core`platform/crud/base-crud.ts`	Slot · many
Spreadsheet bulk editor`store.operate.bulk.bulk_editor`A spreadsheet bulk editor shows many records as rows and columns so staff edit fields across them in one grid.	Plugin	Slot · many

Staff notificationsstore.operate.alertShowThe emails and summaries that tell staff something needs their attention.

How to extend

EventMany side by sideevent.order.paid event.return.requested event.inventory.low_stock event.order.disputedA plugin sends its own staff alert, such as a chat message, by subscribing to the same store events the built-in alerts use.
ProviderOne per storeemail senderStaff alert emails go out through the store's one email sender.

Part	Litestore today	How to extend
Staff notification inbox`store.operate.alert.notification_inbox`The staff notification inbox is the one email address that receives every operational alert the store sends.	Core`app/admin/settings/notifications/page.tsx`	Event · manyProvider · one
Operational alert`store.operate.alert.operator_alert`An operational alert emails staff about a new sale, a payment problem, a return, a stock risk, a customer message or a creator event, and records it in the activity log.	Core`modules/messaging/operator-alert.ts`	Event · manyProvider · one
New message alert`store.operate.alert.message_alert`A new message alert emails staff when a customer writes in, with a link to the conversation.	Core`modules/messaging/alert-emails.ts`	Event · manyProvider · one
Weekly digest`store.operate.alert.weekly_digest`The weekly digest emails staff a summary of the past week's sales, orders and open work.	Core`jobs/cron.weekly-digest.tsx`	Event · manyProvider · one
Team chat alert`store.operate.alert.chat_alert`A team chat alert posts a store event into a channel in a chat tool such as Slack.	Plugin	Event · manyProvider · one

Records and exportsstore.recordsShowThe history of changes in the store and the files staff take out of it.

Activity logstore.records.activityShowThe audit trail of who changed what, and when.

How to extend

Assistant toolMany side by sidesearchActivityThe assistant searches the activity log through the searchActivity tool.
Core onlyWriting activity rows stays in core, because each change records itself at the call site that makes it.

Part	Litestore today	How to extend
Activity entry`store.records.activity.entry`An activity entry records one change, with the record it touched, the staff member or system that made it, and the time.	Core`modules/operations/activity/emit.ts`	Assistant tool · manyCore only
Changed fields`store.records.activity.changed_fields`Changed fields list each field an edit touched with its old and new value.	Core`modules/operations/activity/changed-fields.ts`	Assistant tool · manyCore only
Activity feed`store.records.activity.feed`The activity feed shows the entries for one record, or for the whole store, newest first.	Core`ui/admin/activity-log.tsx`	Assistant tool · manyCore only
Log retention`store.records.activity.retention`Log retention deletes routine activity entries after a set number of days and keeps the entries marked as durable.	Core`jobs/cron.data-cleanup.ts`	Assistant tool · manyCore only

Data exportstore.records.exportShowFiles of store data that staff download for accounting, analysis or moving to another tool.

How to extend

ProviderMany side by sideexport formatA plugin adds another export format or destination, such as a spreadsheet sync, beside the built-in CSV files.

Part	Litestore today	How to extend
Spreadsheet export`store.records.export.spreadsheet_file`A spreadsheet export downloads the selected or filtered products, orders or customers as a CSV file with chosen columns.	Core`modules/integrations/export`	Provider · many
Scheduled export`store.records.export.scheduled_export`A scheduled export builds the same file on a timetable and sends it to an email address or storage folder.	Plugin	Provider · many

Developer accessstore.developerShowThe keys, APIs and outbound calls that let other software read and change the store.

API keys and APIsstore.developer.accessShowHow other software and outside assistants read and change the store.

How to extend

Assistant toolMany side by sideagent tool serverAn outside assistant connects to the store's admin tools over MCP with a scoped key, and change tools only create approval cards.

Part	Litestore today	How to extend
API key`store.developer.access.api_key`An API key is a secret that another program sends with each request, limited to the scopes chosen when the key was made.	Core`modules/team/api-keys/keys.ts`	Assistant tool · many
Key scope`store.developer.access.key_scope`A key scope names what a key may do, such as read the catalog, change carts or write orders.	Core`modules/team/api-keys/scopes.ts`	Assistant tool · many
Store API`store.developer.access.store_api`The store API answers typed requests for products, carts and orders and publishes its description as an OpenAPI file.	Core`platform/api/router.ts`	Assistant tool · many
Agent tool server`store.developer.access.agent_tool_server`The agent tool server lets an outside AI assistant call the store's admin tools over the MCP protocol, with an API key that has the MCP scope.	Core`app/api/mcp/admin/route.ts`	Assistant tool · many
Rate limit`store.developer.access.rate_limit`A rate limit caps how many requests a key, user or address may send in a time window and rejects the rest.	Core`platform/rate-limit/limiters.ts`	Assistant tool · many

Outbound webhooksstore.developer.webhookShowCalls the store sends to another program's address when something happens.

How to extend

EventMany side by sideevent.order.paid event.order.refunded event.product.updated event.customer.createdEach webhook subscribes to store events and sends them to its address.

Part	Litestore today	How to extend
Webhook endpoint`store.developer.webhook.endpoint`A webhook endpoint is an address plus a list of store events, and the store posts each matching event to that address.	Core`modules/integrations/webhooks/crud.ts`	Event · many
Signed delivery`store.developer.webhook.signature`A signed delivery carries a signature made with a shared secret so the receiver checks that the call came from the store.	Core`modules/integrations/webhooks/delivery.ts`	Event · many
Delivery retry`store.developer.webhook.retry`A delivery retry sends a failed webhook again on a schedule and records each attempt in the delivery log.	Core`jobs/cron.webhook-retries.ts`	Event · many
Failing endpoint switch-off`store.developer.webhook.auto_disable`A failing endpoint switch-off turns off a webhook after fifteen failed deliveries in a row.	Core`modules/integrations/webhooks/auto-disable.ts`	Event · many

Running the systemstore.systemShowThe background work and checks that keep the store running between requests.

Background jobs and healthstore.system.jobsShowWork that runs outside a page request, and the checks that show the store is up.

How to extend

EventMany side by sideevent.order.paid event.cart.abandonedA plugin runs its own background work by subscribing to store events, and retries follow the same job runner.
ProviderOne per storejob runnerOne job runner per store queues events, cron jobs and retries.

Part	Litestore today	How to extend
Event job`store.system.jobs.event_job`An event job runs in the background when a store event fires, such as sending emails after an order is paid, and retries on failure.	Core`jobs/domain-events.ts`	Event · manyProvider · one
Scheduled job`store.system.jobs.scheduled_job`A scheduled job runs at a fixed time, such as nightly stock clean-up, payment reconciling or weekly data clean-up.	Core`jobs`	Event · manyProvider · one
Failed job record`store.system.jobs.failed_job`A failed job record writes an activity entry when a background job runs out of retries, so the failure shows in the admin.	Core`jobs/platform.failures.ts`	Event · manyProvider · one
Health check`store.system.jobs.health_check`The health check is a public address that uptime monitors call, and it reports whether the database and cache answer.	Core`app/api/health/route.ts`	Event · manyProvider · one
Connection health`store.system.jobs.connection_health`Connection health shows whether each connected outside service, such as payments or email, has working credentials.	Core`modules/integrations/health.ts`	Event · manyProvider · one
Storefront cache refresh`store.system.jobs.cache_refresh`A storefront cache refresh clears stored copies of storefront pages so the next visit reads fresh data.	Core`modules/storefront/admin/cache-actions.ts`	Event · manyProvider · one

Automation rulesstore.automationShowIf-this-then-that rules a merchant builds from a trigger, conditions and actions, as in workflow automation apps.

Triggerstore.automation.triggerShowWhat starts an automation rule.

How to extend

EventMany side by sideevent.order.paid event.order.created event.customer.created event.inventory.low_stockAn automation plugin starts its rules from the store's domain events.

Part	Litestore today	How to extend
Store event trigger`store.automation.trigger.store_event`A store event trigger starts a rule when a store event fires, such as an order paid or stock running low.	Plugin	Event · many
Schedule trigger`store.automation.trigger.schedule`A schedule trigger starts a rule at a set time or on a repeating timetable chosen by the merchant.	Plugin	Event · many
Incoming call trigger`store.automation.trigger.incoming_call`An incoming call trigger starts a rule when another program posts to the rule's own address.	Plugin	Event · many
Run by hand`store.automation.trigger.manual`A run-by-hand trigger starts a rule when staff press a button on a record or a selection.	Plugin	Event · many

Conditionstore.automation.conditionShowThe checks that settle whether the rule goes on, and which branch it takes.

How to extend

Core onlyConditions belong to the automation plugin that runs the rule; Litestore core has no rule builder.

Part	Litestore today	How to extend
Field check`store.automation.condition.field_check`A field check compares one value from the trigger's record, such as order total or customer tag, against a value with an operator such as greater than.	Plugin	Core only
Otherwise branch`store.automation.condition.branch`An otherwise branch holds the actions that run when the conditions do not match.	Plugin	Core only

Actionstore.automation.actionShowWhat the rule does once it runs.

How to extend

Assistant toolMany side by sideproposeCoupondraftCustomerMessageRules that change store data go through the same proposal tools the assistant uses, so staff approve each change.

Part	Litestore today	How to extend
Change a record`store.automation.action.change_record`A change-a-record action edits store data, such as adding a tag to an order or hiding a product.	Plugin	Assistant tool · many
Send a message`store.automation.action.send_message`A send-a-message action emails staff or a customer, or posts to a team chat channel.	Plugin	Assistant tool · many
Send an HTTP request`store.automation.action.http_request`An HTTP request action posts the rule's data to another program's address.	Plugin	Assistant tool · many
Wait`store.automation.action.wait`A wait action pauses the rule for a set time before the next action runs.	Plugin	Assistant tool · many
Assistant workflow`store.automation.action.assistant_workflow`An assistant workflow is a saved series of assistant tool calls that runs as one rule, with each change shown for approval.	Planned	Assistant tool · many

Run historystore.automation.historyShowThe record of each time a rule ran and what it did.

How to extend

Core onlyRun history belongs to the automation plugin; failed background jobs in core already show in the activity log.

Part	Litestore today	How to extend
Rule run log`store.automation.history.run_log`A rule run log lists each run with its trigger, the branch taken, the actions done and any error.	Plugin	Core only

Phrase	Made of
staff accounts	store.staff.account.staff_member store.staff.account.invitation
staff permissions	store.staff.access.permission store.staff.access.per_person_override
role-based access	store.staff.access.role store.staff.access.permission
custom roles	store.staff.access.custom_role
audit log	store.records.activity.entry store.records.activity.changed_fields store.records.activity.feed
two-factor authentication	store.staff.account.two_factor
login as customer	store.staff.account.impersonation
workflow automation	store.automation.trigger.store_event store.automation.condition.field_check store.automation.action.change_record store.automation.history.run_log
if this then that	store.automation.trigger.store_event store.automation.condition.field_check store.automation.action.change_record
scheduled workflows	store.automation.trigger.schedule store.automation.action.change_record
command palette	store.operate.home.admin_search
bulk actions	store.operate.bulk.batch_action
store setup checklist	store.settings.details.setup_guide
webhooks	store.developer.webhook.endpoint store.developer.webhook.signature store.developer.webhook.retry
API access tokens	store.developer.access.api_key store.developer.access.key_scope

Store administration

What the phrases mean

Phrases left out

Sources