Operations & governance

Run commerce day to day on a platform your team already knows how to operate

Sales, customer service, catalogue, fulfilment, and operations teams work from the Vendure Dashboard. Automation keeps orders moving, while permissions, single sign-on, audit trails, and publishing controls keep the operation governed.

One Vendure Dashboard for the teams running ecommerce

When you replace a commerce system, the biggest hidden risk is not the technology. It is the day the people who run orders, refunds, and customer accounts have to do their job in an unfamiliar tool.

The Vendure Dashboard is the workspace for the people who use the platform all day. Sales, customer service, catalogue, fulfilment, and operations teams manage orders, refunds, returns, customers, products, and exceptions themselves, with roles deciding who sees and does what.

Automation that keeps orders moving

Approvals, fulfilment runs, and order syncs run inside the same platform that runs your catalogue and orders, so operators can watch them, step in, and adapt them as the business changes. Your team builds fulfilment runs and order syncs as workflows on the Workflow Engine in every plan.

Approvals that wait for the right person

From Scale, an order over a spending limit waits for the right person to approve it. On Enterprise, a timeout can approve or reject the request automatically. Operators see where every order sits and can approve or step in from the Dashboard.

Order sync that survives a bad connection

When an order is placed, your order sync workflow sends it to the systems that fulfil and account for it. If a connection drops part way through, the step retries on its own instead of losing the order, and anything that does fail lands in front of an operator with the full history attached.

Scheduled fulfilment with a human checkpoint

A nightly run your team builds on the Workflow Engine batches orders for the warehouse and pauses for a person to confirm before dispatch. Confirm and the orders move; reject and they go back for re-batching.

Governance is in place before the auditor asks

Security wants single sign-on and a complete record of who did what. Compliance wants retention, exports, and proof of who accessed sensitive records. On many platforms, the audit trail is a separate product to wire in.

Vendure builds them into the plans, from Scale upward, on the same platform that runs your ecommerce, so the person who signs in is the person the audit trail records and the permissions apply to.

The controls your security and compliance teams ask for, as standard

Roles and permissions are the foundation. Single sign-on, an audit trail, and access rules extend them on the same platform.

Single sign-on

Your team signs in with the identity provider you already use: Okta, Microsoft Entra ID, Google Workspace, or any OpenID Connect provider. New administrators are created on their first sign-in. When IT removes someone from the identity provider, they can no longer sign in through it. Remove or disable their Vendure administrator as part of offboarding.

Permissions that match your org

Decide who can see and do what, down to the channel, brand, or region. A finance manager, a warehouse lead, and a support agent each get the access their role needs and nothing more.

A complete audit trail

Every change is recorded with who made it, when, and what changed, with sensitive fields removed before anything is stored. Login attempts are captured too, and you can record who viewed sensitive records when a regime requires it.

Data people should not see stays hidden

Access policies narrow which records each administrator can see, for example only orders in certain states or customers in certain groups. Custom conditions cover other rules.

Draft, preview, publish, and roll back changes

From Scale, catalogue records can be saved as drafts, previewed in your storefront, and published when ready.

Version history lets you restore an earlier version of a record, so teams can recover from a mistaken update and answer what changed, who changed it, and when.

FAQ

Who uses the Vendure Dashboard?

Sales, customer service, catalogue, fulfilment, and operations teams use it for the everyday work of running ecommerce. Roles and permissions adapt the information and actions available to each team.

Can operators handle approvals and exceptions without engineering?

Yes. Approvals and exception handling happen in the Dashboard. Operators approve, reject, or step into a stuck process themselves. Engineering gets involved to change how a process works, not to run it day to day.

Which identity providers work with single sign-on?

Any OpenID Connect provider, including Okta, Microsoft Entra ID, Google Workspace, Auth0, Keycloak, OneLogin, and Ping Identity.