Manual orders
It lands on the founder / commercial director first, well before it shows up in any number.
Retail and ecommerce / B2B and digital commerce
Digital systems for marketplace seller businesses
Operloom designs and builds the connected system a marketplace seller runs on: the website, the CRM, the booking and follow up and the reporting, configured as one and handed over documented.
SME / mid marketB2B and digital commerceScheduled workOnline payment
Demand arrives through trade search, account managers and reordering. The system has to be ready for it in the same shape it arrives in.
Primary conversion: Account application, quote, bulk order or repeat purchase
01Commerce
The business reality
The brief for a marketplace seller starts with how the work actually arrives and where it stalls, not with a platform shortlist.
Static catalogues
Left alone it becomes a reporting problem too: the record of what happened gets assembled afterwards, from memory.
Account specific pricing complexity
Because marketplace fees and rules you do not control, against a direct channel you do, this one compounds rather than staying still.
Disconnected ERP and CRM data
Fixing it is rarely a tooling decision. It is a question of where the work is supposed to stop and who picks it up next.
02Commerce
Catalogue, search and product experience
The recommended build is B2B catalogue, account and ordering portal. The modules below are the ones this operating model needs, not a sitemap template.
CatalogueCustomer pricingBulk orderingQuote requestAccount approvalReorderDocuments and support
03Commerce
Checkout, payments and fulfilment
Quoting, invoicing and payment are built as one path rather than three tools, because the gaps between them are where revenue goes missing.
Request a quote
A account asks for pricing with enough detail attached to answer properly.
Approve an estimate
Approval is recorded against the scope it approved.
Pay a deposit
Where a deposit is how the work is committed, it is taken at that point.
Receive an invoice
Raised from the agreed scope, not retyped from it.
Pay online
Without a phone call, and reconciled automatically.
Access receipts
Available to the account rather than requested from you.
View payment status
Visible on the record, so chasing is informed.
Purchase products
A checkout built around the way this catalogue is actually bought.
04Commerce
From discovery to repeat purchase
The primary conversion for a marketplace seller is account application, quote, bulk order or repeat purchase. Everything below is arranged around getting there without losing people, and around knowing afterwards where they went.
- 01
Discovery
A account finds the business through trade search, account managers and reordering.
- 02
Evaluation
They check whether this is the right store for them. This is what account terms, stock accuracy and a reorder that takes seconds is for.
- 03
Payment
Payment is taken online, and its status is on the record rather than in somebody inbox.
- 04
Fulfilment
The order is picked, dispatched and tracked, with the account told at each change of state.
- 05
Review
A review request goes out at the point the account is most likely to mean it.
- 06
Repeat
The next order is prompted deliberately, on the cycle this kind of work actually runs on.
05Commerce
Product discovery and advertising
Discovery for a marketplace seller runs through trade search, account managers and reordering. The channels below are the ones that follow from that, and nothing is included because it is fashionable.
Technical SEO
The foundations: crawlability, speed, structure and the markup that describes what this business is
Service search
Product, category, application and industry pages with structured product data
Local search
Useful for branches, trade counters, depots and service areas
Content
Answering what a account needs to know before they will make contact
Social
Product education, applications, technical proof and channel communication
Paid media
Search, account based and remarketing campaigns
Reviews
Trade references, product reviews and service quality proof
Landing pages
Campaign pages built from the same components, so they are fast to ship and consistent to measure
06Commerce
Lifecycle email and basket recovery
Email only works when it arrives. Authentication and list hygiene come before anything creative, because a message in spam is worse than no message.
Account onboardingProduct updatesReplenishmentQuote follow up and reactivation
07Commerce
Customer records and segmentation
A CRM only earns its place when it is the record everyone trusts. For a marketplace seller that means holding accounts, contacts, tiers, territories, opportunities, quotes, contracts and order history and nothing nobody maintains.
Records
No duplicates, and no separate spreadsheet holding the version people actually trust.
Lifecycle
The stages a account actually moves through here, named the way the team already names them.
Pipeline
Every open order has an owner, a stage and a date. Anything without all three is a fault.
Lead source
Attribution written to the record once, then left alone.
Ownership
Somebody is responsible for every open order, and the system knows who.
Tasks and follow up
Tasks that appear on the right day for the right person, and chase when they do not happen.
Reporting
The measures a marketplace seller is run on, drawn from the same records the team works in.
Permissions
Who can see and change what, decided deliberately rather than by whoever set the account up.
08Commerce
Automation
These are the workflows that carry the repeatable parts of a order. Every one of them has a human review point, because the useful automations are the ones people trust.
01Enquiry capture and routing
TriggerA account submits an account or quote request on any page of the site
ConditionsThe submission passes validation and spam checks, and carries the page, campaign and referral it came from
ActionsCreate or match the account record, attach the source, apply the qualifying answers, assign an owner and start the response clock
Human reviewA person reads every account or quote request before it is answered. Routing decides who, not what they say
DestinationCRM, with an internal notification to the assigned owner
Why it helpsNo account or quote request sits unowned, and the source that produced it survives into the reporting
02Response and follow up
TriggerAn account or quote request has been owned for longer than the agreed response window
ConditionsNo reply has been logged and the record is still open
ActionsEscalate to a second owner, raise a task and flag it on the daily view
Human reviewEscalation notifies a person. It never sends anything to the account on its own
DestinationTask queue and internal alert
Why it helpsSlow replies surface the same day rather than at the end of the month
03Confirmation and reminder sequence
TriggerA delivery slot is booked or rescheduled
ConditionsThe account has a valid contact method and has not opted out of operational messages
ActionsSend confirmation immediately, then reminders on the schedule this kind of delivery slot needs, each with reschedule and cancel links
Human reviewTemplates are approved once. Individual sends are automatic
DestinationEmail and messaging, logged against the account record
Why it helpsFewer missed delivery slots, and a cancellation that arrives early enough for the slot to be refilled
04Reporting refresh
TriggerThe reporting period rolls over
ConditionsSource data has loaded and reconciled
ActionsRefresh the dashboard, recalculate the measures that matter to a marketplace seller, and flag anything that moved beyond its usual range
Human reviewCommentary is written by a person. The numbers are not
DestinationDashboard and scheduled summary
Why it helpsThe same numbers every time, assembled the same way, so a change means something
05Quote to invoice
TriggerA quote is approved by the account
ConditionsScope and price are agreed and recorded on the order
ActionsRaise the invoice from the agreed scope, set the payment terms, send it and track its status against the same record
Human reviewAnything outside the standard scope or discount range goes to a person first
DestinationFinance system and CRM
Why it helpsWhat was agreed and what was billed stay the same document
06Review request
TriggerA order is marked complete
ConditionsThe order completed without an open complaint, and the account has not been asked recently
ActionsWait the interval that suits this kind of work, then send a single request with a direct link
Human reviewSuppression rules are set by a person and applied automatically
DestinationReview platform and account record
Why it helpsReviews are requested consistently rather than when somebody remembers
07Payment and receipt
TriggerA payment succeeds or fails
ConditionsThe payment is matched to an open order or order
ActionsUpdate the status, issue the receipt, release the next step and raise a task on failure
Human reviewFailed payments are worked by a person, not retried silently
DestinationPayment platform, finance system and CRM
Why it helpsPayment status is on the record rather than in a separate inbox
09Commerce
The recommended operating system
The nodes are unremarkable. What makes this an operating system rather than a stack is that each connection is deliberate, owned and documented.
- 01Discovery
Where a account first finds the business.
- 02Website
The pages a account reads before deciding to make contact.
- 03Forms
Qualifying questions asked once, at the point of enquiry.
- 04CRM
Every account, every order and who owns it.
- 05Calendar
Real availability for a order, with the preparation time it needs.
- 06Invoicing
Estimates and invoices raised from the agreed scope.
- 07Payments
Payment taken and reconciled against the record.
- 08Email
Operational and lifecycle messages that arrive and are logged.
- 09Automation
The rules that move work between systems, with human review where it matters.
- 10Portal
What a account can see and do without contacting anyone.
- 11Advertising
Campaigns tracked through to the record they produced.
- 12Analytics
The measures a marketplace seller is actually run on.
- 13Internal alerts
Who is told, when, and what they are expected to do about it.
10Commerce
What Operloom builds
Scope is decided by what the operating model requires, not by what is available. Core is structural for a marketplace seller. Recommended follows shortly after. Optional depends on the year you are having.
19Core services
9Recommended
6Optional
Revenue operations
- CRM setup and data modelcore
CRM setup and data model supports marketplace seller businesses by helping to enable self service ordering
- Pipeline and lifecycle designcore
Pipeline and lifecycle design supports marketplace seller businesses by helping to enable self service ordering
- Lead routing, scoring and follow upcore
Lead routing, scoring and follow up supports marketplace seller businesses by helping to enable self service ordering
Digital presence
- Website build or redesigncore
Website build or redesign supports marketplace seller businesses by helping to enable self service ordering
- Service and landing pagescore
Service and landing pages supports marketplace seller businesses by helping to enable self service ordering
Commerce
- Ecommerce or online orderingcore
Ecommerce or online ordering supports marketplace seller businesses by helping to enable self service ordering
- Online payments and depositscore
Online payments and deposits supports marketplace seller businesses by helping to enable self service ordering
- Memberships and subscriptionsrecommended
- Email infrastructure and deliverabilitycore
Email infrastructure and deliverability supports marketplace seller businesses by helping to enable self service ordering
- Email campaigns, nurture and reminderscore
Email campaigns, nurture and reminders supports marketplace seller businesses by helping to enable self service ordering
Measurement
- Analytics and conversion trackingcore
Analytics and conversion tracking supports marketplace seller businesses by helping to enable self service ordering
- Dashboards and attributioncore
Dashboards and attribution supports marketplace seller businesses by helping to enable self service ordering
Technology
- Platform integrations and APIscore
Platform integrations and APIs supports marketplace seller businesses by helping to enable self service ordering
- Security, privacy and maintenancecore
Security, privacy and maintenance supports marketplace seller businesses by helping to enable self service ordering
Brand
- Brand identity systemcore
Brand identity system supports marketplace seller businesses by helping to enable self service ordering
- Sales and marketing materialsrecommended
Discovery
- Technical and on page SEOcore
Technical and on page SEO supports marketplace seller businesses by helping to enable self service ordering
- Local SEO and Google Business Profileoptional
Content
- Content strategy and copywritingcore
Content strategy and copywriting supports marketplace seller businesses by helping to enable self service ordering
Finance operations
- Quotes, estimates and invoicingcore
Quotes, estimates and invoicing supports marketplace seller businesses by helping to enable self service ordering
Automation
- Workflow automationcore
Workflow automation supports marketplace seller businesses by helping to enable self service ordering
- Practical AI assistants and workflowsrecommended
Customer experience
- Client, patient or customer portalcore
Client, patient or customer portal supports marketplace seller businesses by helping to enable self service ordering
- Live chat, WhatsApp and messagingrecommended
- Help desk and service workflowsrecommended
Social
- Social profile setuprecommended
- Social media operationsoptional
Acquisition
- Paid search campaignsrecommended
- Paid social campaignsrecommended
Operations
- Documents, forms and e signaturerecommended
- Booking and appointment systemoptional
Trust
- Reviews and reputation managementoptional
Scale
- Multi location and franchise managementoptional
- Enterprise governance and data architectureoptional
11Commerce
Where better systems change something
The honest claim is narrow: a well built system makes certain failures much less likely and makes the rest visible. For a marketplace seller the areas below are where that shows up first, each with the measure that would prove it.
Response time
Cutting the gap between an account or quote request arriving and a person answering it, which is usually the single largest lever.
Measure: Account acquisitionOperational control
Being able to change how the work runs without needing the person who originally set it up.
Measure: Quote conversionRevenue visibility
Knowing what is committed, what is quoted and what is at risk, without rebuilding the picture by hand each month.
Measure: Order valueAdministrative efficiency
Taking the repeatable parts of the order out of somebody's head and putting them into a workflow that runs whether or not it is a busy week.
Measure: Reorder rateLead quality
Asking the qualifying questions at the point of enquiry, so the order is scoped before anyone spends time on it.
Measure: Channel and product performanceVisibility
Being findable for the terms a account actually uses, rather than the ones the business uses internally.
Measure: Account acquisition12Commerce
Commerce analytics and repeat purchase
Reporting is built around the decisions the business actually makes. For a marketplace seller that is a short list, which is the point.
Account acquisition
Reviewed alongside the stage it depends on, not in isolation.
Quote conversion
Broken down by source, so the number leads somewhere.
Order value
Tracked as a trend, because a single period rarely means anything.
Reorder rate
Defined once and written down, so it means the same thing next quarter.
Channel and product performance
Measured from the record rather than reconstructed at month end.
13Commerce
How Operloom works
- 01
Assess
A short audit of the platforms, the data in them and the points where an account or quote request stalls.
- 02
Design
The operating model on paper first: stages, ownership, definitions and the measures that will judge it.
- 03
Implement
Built in the order that gets a marketplace seller value soonest, not the order that is tidiest to build.
- 04
Connect
Connections built with retry, logging and a defined failure path, so a break is visible rather than silent.
- 05
Document
Everything written down, because a system only one person understands is a risk rather than an asset.
- 06
Measure
Instrumented against account acquisition, quote conversion and order value, with the definitions agreed first.
- 07
Improve
A review cadence with a short list of changes, run against the same measures each time.
14Commerce
What you end up with
Concrete deliverables, not projected commercial results. What each one achieves depends on how it is used after handover.
B2B catalogue, account and ordering portalBrand and component system as requiredCRM configuration, pipeline and field definitionsBooking workflows, availability rules and reminder sequencesQuote and invoice templates linked to the recordPayment configuration and reconciliationAuthenticated email setup and lifecycle templatesAutomation workflows with documented review pointsTracking plan, event taxonomy and dashboardsSelf service area scoped to what is genuinely usefulIntegration configuration and failure handlingDocumentation, workflow maps and handover trainingLaunch support and an agreed review cadence
15Commerce
Recommended package
Recommended starting scope
B2B Commerce and Revenue Operations
A starting scope rather than a fixed package. The plan page sets out who it is for, the core deliverables, the modules, the integrations and the measures.
Core measures
- Account acquisition
- Quote conversion
- Order value
- Reorder rate
- Channel and product performance
Custom scope
Scope varies with what already exists, so we do not publish a figure. Tell us what you have and you will get a scoped proposal with the assumptions written down.
- Support level
- Agreed per engagement
- Contract term
- Agreed per engagement
- Implementation
- Agreed after scoping
16Commerce
Typical integrations
The categories this operating model usually has to connect. Naming a category is not a claim of partnership, certification or reseller status.
ERPInventoryCRMPricingPaymentsLogisticsAccounting and product information systems
17Commerce
Compliance, privacy and risk
Tax, trade, product, credit, privacy and customer specific terms.
That is a factual summary of the areas that tend to apply, not advice. Requirements vary by jurisdiction and change. We build to what your advisers confirm applies, and we implement it properly: consent capture, retention, access control, audit trails and secure handling.
18Commerce
Frequently asked questions
Question: How do you handle the regulatory side?
Operloom replies:
Carefully, and within our lane. Tax, trade, product, credit, privacy and customer specific terms. We build to what your advisers tell us applies: consent capture, retention rules, access control, audit trails and secure handling. We implement requirements. We do not interpret them for you, and we will say so rather than guess.
Question: Can we keep the website and CRM we already have?
Operloom replies:
Often, yes, and it usually makes the project smaller. A maintainable site is better connected than replaced: account or quote request capture that carries its source, tracking that survives, and a clean handover into the CRM. The CRM question is whether it can hold accounts, contacts, tiers, territories, opportunities, quotes, contracts and order history without being fought. If it can, we configure it properly. If it cannot, we say so and explain what migrating would actually cost you in time and disruption.
Question: How is this different from just installing a store platform?
Operloom replies:
The platform is the easy part. What decides whether the store works is everything around it: how a account finds the right product, whether stock information is true, whether checkout loses people, and whether the second order is prompted deliberately. Those are configuration and integration questions, not platform questions.
Question: What do you need from us?
Operloom replies:
Less than most people expect, but not nothing. Access to the platforms, a decision maker who can settle scope questions in the same week they are asked, and someone who knows how the work really runs, which is rarely the same as how it is written down. Content and assets where you have them. We write what you do not.
Question: How does booking connect to everything else?
Operloom replies:
Availability comes from the real calendar, not a copy of it, so a order cannot be booked into a slot that is already gone. Sales, product or technical consultations. Every booking writes back to the account record, so the diary and the pipeline are the same story.
Question: What does Operloom actually build for a marketplace seller?
Operloom replies:
The scope starts from how this kind of business runs rather than from a package. In practice that means B2B catalogue, account and ordering portal, a CRM holding accounts, contacts, tiers, territories, opportunities, quotes, contracts and order history, and the booking and follow up around it. The nearest starting point in our catalogue is B2B Commerce and Revenue Operations, which is a scope to argue with rather than a fixed list.
Question: How long does an implementation take?
Operloom replies:
It depends on how much already exists and how clean it is. A build is sequenced so that something useful goes live early rather than everything landing at once: the CRM and account or quote request capture first, because that is where work is lost today, then the site, then the automation, then reporting. We give a timeline after a scoping conversation, not before one.
Question: What happens after launch?
Operloom replies:
You get the documentation, the workflow map and the training, because the point is that you own it. Ongoing support is a separate arrangement rather than an assumption: some businesses take a maintenance and improvement retainer, others take the handover and run it themselves. Both are fine, and we will tell you which one we think fits.
Scope this against your actual systems
Tell us what a order looks like now, end to end. That conversation usually makes the scope obvious, and sometimes makes it smaller.