Skip to main content
Configure is the setup surface inside 247CloudHub. Fifteen pages where the merchant wires up marketplaces, organisation details, document templates, workflows, pricing rules, permissions, and shipping. The action verb is [Configure]. What makes Configure load-bearing in the CloudHub design is that every action-verb service relies on it. Compete reads from Compete Pricing Rules. Deliver reads from Deliver Order Stages Settings. Optimise reads from Optimise Profiles. Locate, Analyse, and the Customer Services console all read role permissions, marketplace credentials, and template definitions configured here. Configure is the wiring hub that ties the verbs together.

​
The fifteen configuration surfaces

Grouped into four working categories:

​
Marketplace and organisation

See Marketplace and Organisation.

​
Templates and documents

See Templates and Documents.

​
Workflows, pricing rules, and profiles

See Workflows and Pricing Rules.

​
Permissions and shipping

See Permissions and Shipping.

​
How Configure feeds the action verbs

This is the load-bearing relationship in the CloudHub design. The service-pages-as-action-verbs design works because Configure is the single wiring surface. A merchant who sets up Configure once does not have to revisit per-verb settings; the verbs read from the central source.

​
How merchants use the Configure module

Three patterns:
  1. Day-zero setup. Walk the four categories in order. Marketplace Accounts first (so feeds start syncing), Organisation Settings (so VAT and currency are right), then Templates and Documents (so dispatch can run), then Workflows and Pricing Rules (so orders process and prices respond), then Permissions and Shipping (so the team is access-controlled and the carriers are wired).
  2. Routine adjustments. A new marketplace launch (add to Marketplace Accounts), a new template revision (Invoice Templates), a new staff member (User Permissions). Routine moves that do not require re-touching the rest.
  3. Quarterly review. The configuration drifts over time: stale workflow rules, expired user accounts, deprecated marketplace credentials. A quarterly Configure review keeps the wiring clean.

​
Common questions

Do I need to configure all 15 surfaces before going live? At minimum: Marketplace Accounts, Organisation Settings, Email and FTP Settings, Order Workflow (default profile is fine), one of each of Invoice/Picking/Shipping Note templates, and User Permissions for at least one user. Repricing, Optimise Profiles, and Compete Pricing Rules are activated when you turn on the relevant action verb. Can I export and re-import my Configure setup to a sandbox? Most surfaces have export/import paths through CSV; some are workspace-specific and must be re-entered. The pattern is to mirror the live workspace into a staging workspace and reconfigure rather than to sync the two. Where do API keys and webhook secrets live? Marketplace credentials live in Marketplace Accounts (one per marketplace account). SMTP and FTP credentials live in Email and FTP Settings. They are never displayed once saved; rotation is via re-entry. Who should have permission to edit Configure? Restrict by role. Most workspaces grant Configure-edit to a single Admin role and grant Configure-read to managers. CS agents and warehouse staff typically have no Configure access at all.

​
Next steps