Contact Platform
Menu

Cloudstore Platform

Order Management & Orchestration

Keep every order, job, production destination and shipment connected.

Cloudstore coordinates orders from connected sales and business systems, validates the required products and assets, creates the production jobs needed for fulfilment and maintains one consolidated view across production, packing, shipping and delivery. Authorised stakeholders can follow the status and exceptions relevant to their roles throughout the complete lifecycle.

Cloudstore maintains one consolidated order view even when fulfilment requires multiple order lines, production jobs, facilities, packages or shipments.

Order intake

One place for orders from every connected channel

Orders may enter Cloudstore from a range of connected sources, where supported and configured. Cloudstore does not require every channel to be present.

Ecommerce storefrontsWeb-to-print portalsRetail systemsCorporate ordering portalsMarketplace connectionsCustomer-service order entryTrade ordering systemsAPI-connected applicationsExternal order-management systemsERP or procurement systems

Incoming data may include, where supplied and supported:

  • Customer reference
  • Customer details
  • Delivery information
  • Billing information where required
  • Order lines
  • Product variants
  • Quantities
  • Digital assets
  • Product configuration
  • Pricing information
  • Payment status where integrated
  • Required delivery service
  • Due dates
  • Approval requirements
  • Special production instructions
  • Rights and permission references

The order hierarchy

From one customer order to every job and shipment required to fulfil it

A consolidated parent order can relate to many lines, jobs, destinations, packages and shipments — without losing the connection between them.

How one consolidated order relates to its lines, jobs, destinations, packages and shipments.

Customer order

  • Customer order
    • Order line 1
      • Production job A
      • Production job B
    • Order line 2
      • Production job C
    • Order line 3
      • Production job D
      • Production job E

Production jobs route to destinations

  • Production facility 1
  • Production facility 2
  • Specialist finishing partner

Completed work is packed and shipped

  • Package 1 Shipment 1
  • Package 2 Shipment 2

All records remain connected to one consolidated parent order.

  • One order may contain multiple order lines.
  • One line may require multiple production operations.
  • One order may create several production jobs.
  • Jobs may be routed to different destinations.
  • Jobs may complete at different times.
  • An order may be partially completed.
  • An order may have multiple packages.
  • An order may have multiple shipments.
  • Cloudstore preserves the relationship between every record.

Not every order is split or distributed. Many orders are produced as a single job at a single destination; the model simply supports more complex cases when they occur.

Illustrative workflow

Follow one order through orchestration

An accessible, illustrative walk-through of how a single order is coordinated. All information is present in the page; the controls below simply change the view.

Illustrative workflow

A sample order shown to illustrate orchestration.

Order
CS-10482
Order lines
3
Production jobs
5
Production Sites
3
Packages
2
Shipments
2
Combined views
1

Order overview

Order CS-10482 contains three order lines that generate five production jobs across three destinations, resulting in two packages and two shipments — all held within one consolidated parent-order view.

Even where fulfilment is split across jobs, locations, packages and shipments, the order stays connected as one consolidated record.

Order lines

  • Order line 1: Framed fine-art print

    Operations

    PrintQuality controlFramingPacking

  • Order line 2: Canvas wrap

    Operations

    PrintStretchingQuality controlPacking

  • Order line 3: Poster

    Operations

    PrintTrimmingPacking

Production jobs

JobOrder lineDestinationIllustrative status
Production job AOrder line 1Production Site AComplete
Production job BOrder line 1Framing Partner BQuality control
Production job COrder line 2Production Site AReprint required
Production job DOrder line 3Regional Print Site CComplete
Production job EOrder line 3Regional Print Site CPacked

Production destinations

  • Production Site A

    Production jobs A and C (print and quality control)

  • Framing Partner B

    Production job B (specialist framing and finishing)

  • Regional Print Site C

    Production jobs D and E (print, trimming and packing)

Illustrative destination names. No real production partners are named.

Shipments

  • Package 1 → Shipment 1

    Framed fine-art print and poster

    Separate tracking reference

  • Package 2 → Shipment 2

    Canvas wrap

    Separate tracking reference

Exceptions

An illustrative exception on one job does not make completed jobs appear unfinished. The exception stays connected to the affected job and its parent order.

  1. Quality-control issue
  2. Reprint required
  3. Replacement job created
  4. Job reassigned
  5. Reprint completed

Job C raised a quality-control issue and required a reprint; jobs A, D and E remained complete.

Stakeholder views

View as

This demonstration shows an illustrative permissions model. Actual access is determined by each Cloudstore deployment.

  • Ecommerce operator

    May see

    • Order receipt
    • Validation status
    • Production progress
    • Dispatch
    • Tracking
    • Delivery
    • Customer-facing exceptions

  • Customer service

    May see

    • Consolidated order timeline
    • Job dependencies
    • Holds
    • Delays
    • Reprints
    • Shipment tracking
    • Delivery exceptions

  • Production manager

    May see

    • Job and production status across authorised facilities
    • Capacity and workload
    • Production exceptions
    • Rerouting
    • Due dates

  • Print provider

    May see

    • Assigned job
    • Required production assets
    • Production instructions
    • Priority
    • Due date
    • Status controls
    • Exception reporting

  • Rights owner

    May see

    • Authorised production activity
    • Usage records
    • Edition activity
    • Royalty reporting

  • Trade customer

    May see

    • Order status
    • Line-level status
    • Partial completion
    • Dispatch status
    • Consolidated tracking

  • End customer

    May see

    • Order accepted
    • In production
    • Dispatched
    • Tracking
    • Delivered

Illustrative status timeline

  1. Order received
  2. Validated
  3. Jobs created
  4. Production assigned
  5. Printing
  6. Finishing
  7. Quality control
  8. Partially complete
  9. Package created
  10. Partially dispatched
  11. All jobs complete
  12. Final shipment dispatched
  13. Delivered

Exception branch

  1. Quality-control issue
  2. Reprint required
  3. Replacement job created
  4. Job reassigned
  5. Reprint completed

Statuses are illustrative and require alignment with the actual Cloudstore data model. Status is conveyed with text and icons, not colour alone.

Validation

Validate the order before production begins

Before jobs are created, Cloudstore can validate the order against a range of checks, where configured.

  • Required customer information
  • Delivery address
  • Product availability
  • Product configuration
  • Digital asset association
  • File availability
  • Rights and usage permissions
  • Territory restrictions
  • Edition availability
  • Pricing rules
  • Payment status
  • Approval requirements
  • Production capability
  • Shipping eligibility
  • Required completion date

Validation can produce a range of outcomes:

  • Validated
  • Awaiting information
  • Awaiting artwork
  • Awaiting approval
  • On hold
  • Rights conflict
  • Product configuration exception
  • Payment hold where integrated
  • Ready for job creation
  • Cancelled

Status terminology is illustrative. The exact status terminology must be confirmed against the real Cloudstore status model.

Job creation

Convert commercial orders into controlled production jobs

Cloudstore can create the production jobs and operations needed to fulfil each order, with the detail each job requires.

  • Job creation from order lines
  • Print jobs
  • Finishing jobs
  • Framing jobs
  • Quality-control operations
  • Packing operations
  • Specialist production operations
  • Dependencies between jobs
  • Job sequence
  • Quantity
  • Priority
  • Due date
  • Production instructions
  • Required asset
  • Required media
  • Required finishing
  • Required packaging
  • Associated customer and order references

A production job should contain the information required by its authorised production destination without unnecessarily exposing unrelated order or customer information.

Assignment & routing

Route each job to an appropriate production destination

Assignment may consider a range of factors, where available, and supports automatic, rules-based and manual approaches.

  • Product capability
  • Print technology
  • Media availability
  • Finishing capability
  • Framing capability
  • Production capacity
  • Current workload
  • Facility location
  • Delivery destination
  • Rights restrictions
  • Customer requirements
  • Service level
  • Due date
  • Production cost
  • Shipping cost
  • Quality requirements
  • Partner authorisation
  • Manual routing rules

Routing approaches can include:

Automatic routingRules-based routingManual assignmentManual overrideRerouting after an exceptionReassignment when capacity or capability changes

Routing may use configured rules and connected operational information according to the deployment. Not every deployment uses intelligent or live routing.

Status model

Follow the order and every associated production job

Order, production-job and shipment status are related but distinct. The labels below are illustrative.

Order status

  • Received
  • Validating
  • Awaiting information
  • Awaiting approval
  • Approved
  • In production
  • Partially complete
  • Ready for dispatch
  • Partially dispatched
  • Dispatched
  • Delivered
  • On hold
  • Exception
  • Cancelled

Production-job status

  • Created
  • Assigned
  • Awaiting asset
  • Preflight
  • Ready for production
  • Queued
  • Printing
  • Finishing
  • Quality control
  • Packed
  • Complete
  • Failed
  • Reprint required
  • Exception

Shipment status

  • Awaiting shipment
  • Label requested
  • Label created
  • Ready for collection
  • Collected
  • In transit
  • Out for delivery
  • Delivered
  • Delivery exception
  • Returned
  • Parent-order status is derived from associated activities.
  • Child jobs can have different statuses.
  • One failed job should not make completed jobs appear unfinished.
  • Partial completion should remain visible.
  • Shipment and delivery status should remain connected to the original order.
  • Status update frequency may depend on the connected system.

Cloudstore provides live or regularly updated status visibility; not every status is instant or real-time on every integration.

All statuses shown here are illustrative and require alignment with the actual Cloudstore data model.

Shared visibility

One shared operational view with role-appropriate access

Authorised users may include many roles — they do not all see the same information.

Ecommerce operatorsRetail teamsCustomer-service teamsAccount managersProduction managersPrint service providersFinishing and framing partnersFulfilment teamsShipping teamsContent ownersRights holdersFinance teamsRoyalty administratorsTrade customersEnd customers

Ecommerce operator

May see

  • Order receipt
  • Validation status
  • Production progress
  • Dispatch
  • Tracking
  • Delivery
  • Customer-facing exceptions

Customer service

May see

  • Consolidated order timeline
  • Job dependencies
  • Holds
  • Delays
  • Reprints
  • Shipment tracking
  • Delivery exceptions

Production manager

May see

  • Job and production status across authorised facilities
  • Capacity and workload
  • Production exceptions
  • Rerouting
  • Due dates

Print provider

May see

  • Assigned job
  • Required production assets
  • Production instructions
  • Priority
  • Due date
  • Status controls
  • Exception reporting

Rights owner

May see

  • Authorised production activity
  • Usage records
  • Edition activity
  • Royalty reporting

Trade customer

May see

  • Order status
  • Line-level status
  • Partial completion
  • Dispatch status
  • Consolidated tracking

End customer

May see

  • Order accepted
  • In production
  • Dispatched
  • Tracking
  • Delivered

Full lifecycle visibility does not mean unrestricted access. Cloudstore presents information according to each participant’s role, responsibilities and permissions.

Exceptions

Keep exceptions connected to the affected order and job

When something does not go to plan, the exception is surfaced and kept linked to the work it affects.

  • Missing customer information
  • Invalid delivery address
  • Missing artwork
  • Failed file validation
  • Rights conflict
  • Edition limit reached
  • Approval not received
  • Product unavailable
  • Media unavailable
  • Production site unavailable
  • Printer failure
  • Production delay
  • Quality failure
  • Reprint required
  • Packing problem
  • Shipping label failure
  • Carrier delay
  • Failed delivery
  • Return
  • Cancellation
  • Refund or credit requirement where integrated

Each exception remains connected along a clear chain:

  1. Exception
  2. Parent order
  3. Affected order line
  4. Affected production job
  5. Production or shipping destination
  6. Responsible stakeholder
  7. Resolution and status history

Possible actions include:

  • Assign an owner
  • Add a note
  • Place an order or job on hold
  • Request missing information
  • Change priority
  • Reroute a job
  • Create a reprint
  • Cancel an affected item
  • Update the customer-facing status
  • Record a resolution
  • Retain the event history

Surfacing an exception helps the right team act on it; not every exception is resolved automatically.

Explore Shared Visibility & Exception Management

Reprints & changes

Preserve the history when an order changes

When an order changes, the order model should retain the relationship between the original work and what replaced it:

  • Original order
  • Original job
  • Failed or rejected production
  • Reprint job
  • Replacement shipment
  • Cancellation
  • Credit or refund reference where integrated
  • Reason
  • Responsible party
  • Resolution date
  • Final outcome

A reprint should not erase the original job history, and a cancelled line should remain visible in the audit history even when no further production occurs.

Where specific Cloudstore implementation details still require confirmation, this behaviour is described cautiously.

Shipping

Keep dispatch and tracking connected to the production record

Cloudstore may connect an order and its jobs to package, shipping and delivery records, where supported and configured.

  • Package records
  • Package dimensions
  • Package weight
  • Shipping service
  • Shipping label
  • Carrier reference
  • Tracking number
  • Collection status
  • Delivery estimate
  • Delivery status
  • Delivery exception
  • Return
  • Proof of delivery where supported
  • One order may have multiple packages.
  • Packages may contain products from different jobs.
  • A production job may contribute to a package.
  • One package normally has one shipment record.
  • Multiple shipments remain visible under the parent order.
  • Tracking updates should not replace the production history.

Explore Shipping & Fulfilment Integration

Integrations

Connect order events with the wider business ecosystem

Order events can be exchanged with connected systems across the business, where supported and configured.

EcommerceWeb-to-printRetail systemsCorporate procurementMarketplacesERPMISCRMProduction workflowRIP and print systemsWarehouse systemsShipping systemsCarriersAccountingAnalyticsCustomer notification systems

Integration may use:

APIsWebhooksScheduled data exchangeFile-based integrationApproved custom connectors

Available integration

Connections that exist today, where supported and configured.

Configurable integration

Connections that can be enabled and configured for a deployment.

Custom integration

Connections built for specific systems through approved custom connectors.

Planned integration

Connections under consideration but not yet available.

Not all integrations already exist. Some are available, some are configurable, some are custom and some are planned.

APIs & integrations

History

Retain a clear history of the complete order lifecycle

An operational history, or traceable activity record, can capture the events that shaped an order.

  • Order received
  • Order changed
  • Approval requested
  • Approval granted
  • Job created
  • Job assigned
  • Status changed
  • Hold added
  • Hold removed
  • Exception created
  • Exception resolved
  • Job rerouted
  • Reprint created
  • Package created
  • Label generated
  • Shipment dispatched
  • Delivery confirmed
  • Order completed
  • Order cancelled

The visible history depends on user permissions. This is described as an operational history rather than a legally compliant audit trail unless that status has been formally confirmed.

Business value

What connected Order Management makes possible

One consolidated order view

A single parent-order view, even when fulfilment spans many jobs, locations and shipments.

Fewer disconnected status updates

Order, job and shipment status are related rather than scattered across systems.

Clear order-to-job relationships

Every production job remains linked to its order line and parent order.

Better production coordination

Dependencies, priorities and due dates are coordinated across jobs.

Support for split production

One order can be produced across multiple destinations without losing its parent view.

Connected shipping and tracking

Packages, shipments and tracking references stay linked to the production record.

Faster exception identification

Problems are surfaced and kept linked to the work and team they affect.

Role-based stakeholder visibility

Authorised stakeholders see information relevant to their role and permissions.

Traceable reprints and replacements

Reprints and replacements are recorded without erasing the original history.

More complete operational reporting

Consolidated records support operational reporting where configured.

FAQs

Order Management questions

Concise, cautious answers to common questions about how Cloudstore coordinates orders.

Order Management is the platform capability that receives orders from connected channels, validates them, creates the production jobs needed for fulfilment, coordinates routing, shipping and delivery, and maintains one consolidated view of the parent order throughout its lifecycle.

Yes. A single order may contain multiple order lines, and a line may require several operations, so one order can generate multiple production jobs with their own dependencies, priorities and due dates.

Where supported and configured, jobs from one order may be routed to different authorised production destinations. Cloudstore keeps every job linked to its parent order even when production is distributed.

Order lines, production jobs, packages, shipments, exceptions and history are all related to a single parent order, so authorised stakeholders can see consolidated progress even when fulfilment is split across jobs and locations.

Yes. An order may be partially completed and dispatched in more than one package and shipment. Each shipment remains visible under the parent order, with its own tracking reference.

Status may be returned from connected production and shipping systems. Update frequency can vary by system, so Cloudstore provides live or regularly updated status visibility rather than guaranteed real-time updates on every integration.

Yes. Full lifecycle visibility does not mean unrestricted access. Cloudstore presents information according to each participant’s role, responsibilities and permissions, so different stakeholders see different information.

A reprint or replacement is linked to the original order and job and retains the original history, including the reason, responsible party and outcome, rather than overwriting the original record.

Where supported and configured, Cloudstore can exchange order events with external systems through APIs, webhooks, scheduled data exchange, file-based integration or approved custom connectors. Not all integrations exist by default.

No. Cloudstore may integrate with existing business systems and should not automatically be presented as a replacement for every ERP or MIS capability. The right approach depends on the deployment.

Coordinate every order from receipt to final delivery

Talk to us about your order sources, products, production network, shipping systems, stakeholder roles and exception-handling requirements.

Speak to a Cloudstore expert See How Cloudstore Works