Cloudstore Platform
Shared Visibility & Exception Management
Give every authorised stakeholder a connected view of progress, status and exceptions. Cloudstore brings together order, job, production, fulfilment, shipment and delivery information from connected systems. Authorised stakeholders can follow the status, dependencies and exceptions relevant to their roles without losing the relationship between the original order and every associated job, package and shipment.
One lifecycle
Follow the complete lifecycle without losing the relationship between records
Cloudstore can maintain the relationships between every record in the order lifecycle, so the consolidated view never loses sight of how work fits together.
- Parent order
- Order lines
- Production jobs
- Production destinations
- Finishing and quality control
- Packages
- Shipments
- Tracking and delivery events
- Exceptions, reprints, returns and replacements
The consolidated view should be able to answer:
- What was ordered?
- Which lines are complete?
- Which jobs are still active?
- Where is each job being produced?
- Which jobs depend on other jobs?
- Which products have passed quality control?
- Which products have been packed?
- Which shipments have been dispatched?
- Which deliveries are complete?
- Which exception is preventing completion?
- Who is responsible for the next action?
- What has already happened?
- What information can the current user see?
Not every Cloudstore deployment necessarily exposes every record type. Visibility is configured according to the deployment, workflow and data-governance requirements.
Status layers
Keep order, job, package and shipment status distinct
Four status layers stay separate but connected. These are illustrative status terms that require alignment with the actual Cloudstore data model.
Order status
- Received
- Validating
- Awaiting information
- Awaiting approval
- Approved
- In production
- Partially complete
- Ready for dispatch
- Partially dispatched
- Dispatched
- Partially delivered
- 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
Package status
- Awaiting products
- Ready for packing
- Packing
- Packed
- Shipping requested
- Label created
- Ready for collection
- Exception
Shipment status
- Awaiting shipment
- Ready for collection
- Collected
- In transit
- Out for delivery
- Delivered
- Delivery exception
- Returned
- Cancelled
- Parent-order status may be derived from multiple related records.
- Different jobs can hold different statuses at the same time.
- One completed job does not imply that the whole order is finished.
- One delivered shipment does not imply that every shipment is delivered.
- Partial completion must remain visible.
- Exceptions should not erase completed activity.
- Customer-facing statuses may be simpler than operational statuses.
Consolidated order
Maintain one order view across multiple jobs, locations and shipments
An illustrative parent order shows how completed work, current work, dependencies, partial dispatch and an active exception stay within one view.
Parent order CS-10482
- Order CS-10482
- Line 1 — Framed fine-art print
- Print job A — Complete
- Framing job B — In progress (due tomorrow)
- Line 2 — Canvas wrap
- Canvas print job C — Complete
- Stretching job E — Complete
- Package 1 — Packed Shipment 1 — In transit
- Line 3 — Poster
- Poster job D — Quality-control exception
- Reprint job D2 — Queued (replacement)
- Shipment — Awaiting production
- Line 1 — Framed fine-art print
Parent-order status: Partially dispatched — action required.
- Completed work
- Current work
- Dependencies
- Partial dispatch
- Active exception
- Reprint activity
- Shipment progress
- Next required action
Interactive demonstration
Explore one order from several stakeholder perspectives
Use the views below to follow order CS-10482 across its lines, jobs, packages, shipments, timeline, exception and stakeholder views. Every view works without JavaScript; the controls only enhance an existing, accessible page.
Illustrative workflow
One sample order shown from several stakeholder perspectives, to illustrate how order, job, package, shipment and exception information stay connected in a single consolidated view.
- Order
- CS-10482
- Order lines
- 3
- Production jobs
- 5
- Production sites
- 3
- Packages
- 2
- Shipments
- 2
- Active exception
- 1
- Replacement job
- 1
Consolidated order
Order CS-10482 holds three order lines that produce five jobs across three production destinations, with two packages and two shipments — all kept within one consolidated parent-order view.
Parent order CS-10482
- Order CS-10482
- Line 1 — Framed fine-art print
- Print job A — Complete
- Framing job B — In progress (due tomorrow)
- Line 2 — Canvas wrap
- Canvas print job C — Complete
- Stretching job E — Complete
- Package 1 — Packed Shipment 1 — In transit
- Line 3 — Poster
- Poster job D — Quality-control exception
- Reprint job D2 — Queued (replacement)
- Shipment — Awaiting production
- Line 1 — Framed fine-art print
Parent-order status: Partially dispatched — action required.
Order lines
| Order line | Status | Detail |
|---|---|---|
| 1 — Framed art | Production | Print job complete; framing in progress, due tomorrow. No exception. |
| 2 — Canvas wrap | Dispatched | Production complete and packed. Shipment 1 in transit with tracking available. |
| 3 — Poster | Exception | QC failure on the original job. Replacement job created and queued at Production Site C; shipment awaiting production. |
Partial completion stays visible: one line is dispatched, one is in production and one is held by an exception, without losing the relationship to the parent order.
Production jobs
| Job | Order line | Production destination | Illustrative status |
|---|---|---|---|
| Print job A | Line 1 | Production Site A | Complete |
| Framing job B | Line 1 | Production Site A | In progress |
| Canvas print job C | Line 2 | Production Site B | Complete |
| Stretching job E | Line 2 | Production Site B | Complete |
| Poster job D | Line 3 | Production Site C | Quality-control exception |
| Reprint job D2 (replacement) | Line 3 | Production Site C | Queued |
Illustrative destination names. No real production partners are named. The replacement job stays linked to the original Poster job D.
Packages & shipments
Package 1 — Canvas wrap (Line 2)
Package 2 — Framed print and poster (Lines 1 and 3)
Partial dispatch is visible: Shipment 1 is in transit while Shipment 2 is still awaiting production. A delivered shipment does not imply the whole order is complete.
Operational timeline
An illustrative traceable activity record for the order so far — what has happened, in order:
- Order received
- Order validated
- Approval granted
- Jobs created
- Print job A completed
- Line 1 quality check passed
- Framing started (Line 1)
- Canvas printed and stretched (Line 2)
- Package 1 packed
- Shipment 1 dispatched
- Shipment 1 in transit
- Poster job D quality-control failure (Line 3)
- Poster job D placed on hold
- Exception assigned to Production Site C
- Reprint approved
- Replacement job D2 created
- Replacement job D2 queued
Operational history, not a legally compliant audit trail. Update frequency depends on each connected system.
Active exceptions
Illustrative exception workflow — not customer data
Quality-control failure — Poster job D
- Exception ID
- QC-10482-03
- Severity
- High
- Status
- Corrective action in progress
- Date raised
- Day 2, 09:14 (illustrative)
- Parent order
- CS-10482
- Affected line
- Line 3 — Poster
- Affected job
- Poster job D
- Production destination
- Production Site C
- Assigned team
- Production Site C quality team
- Customer impact
- One order line delayed; other items already dispatched
- Required action
- Reprint poster and re-run quality control
- Due date
- Day 4 (illustrative)
- Current resolution status
- Replacement job queued
Illustrative resolution timeline
- Quality-control failure detected
- Job placed on hold
- Exception assigned
- Reprint approved
- Replacement job created
- Replacement job queued
- Reprint completed
- Quality control passed
- Exception resolved
- Shipment released
The live status of this illustrative exception is “Replacement job queued”. The controls only move through a sample sequence; they do not change any real record.
Stakeholder views
This demonstration illustrates a potential permissions model. Actual access is defined by each Cloudstore deployment.
Ecommerce operator
- Order CS-10482 received and validated
- Line and product status
- Line 2 dispatched, in transit
- Line 1 in production
- Line 3 delayed by a production issue
- Customer-facing exception note
Customer service
- Full consolidated order timeline
- All job statuses
- Packages and tracking
- Active quality exception on Line 3
- Responsible team (Production Site C)
- Customer-facing impact: one item delayed
Production manager
- Assigned facilities A, B and C
- Queue status and due dates
- Framing job B due tomorrow
- Quality failure and reprint at Site C
- Dependencies between jobs
- Rerouting and capacity activity
Print provider
- Only the reprint job assigned to this provider
- Required production assets
- Production instructions
- Due date and status controls
- The quality-control exception to act on
Restricted: unrelated customer, cost and rights-sensitive information is not shown.
Fulfilment team
- Line 2 packed into Package 1
- Shipment 1 label and collection status
- Package 2 awaiting products
- Delivery exceptions where they occur
Rights owner
- Authorised production activity for the artwork
- Product usage and edition activity
- Territory information
- Royalty status where configured
Restricted: recipient details are not shown unless required and authorised.
Finance and royalty team
- Commercial references for CS-10482
- Production and shipping costs where permitted
- Royalty records
- The exception affecting financial processing (reprint cost)
Trade customer
- Parent-order status: partially dispatched
- Order-line status and partial completion
- Tracking for the dispatched line
- Delivery progress
End customer
- Order accepted
- Partially dispatched
- Tracking for dispatched items
- Remaining item in production
- Revised delivery information where approved
Resolution history
The active quality exception keeps its own connected resolution history, retained as the corrective work progresses:
- Quality-control failure detected
- Job placed on hold
- Exception assigned
- Reprint approved
- Replacement job created
- Replacement job queued
- Reprint completed
- Quality control passed
- Exception resolved
- Shipment released
Corrective action does not erase the original event. The reprint stays linked to the original Poster job D, and the cancelled or failed work remains in the operational history.
Role-based visibility
Show each stakeholder the information relevant to their role
Visibility may be controlled by a range of factors, so different stakeholders do not necessarily see the same information.
Ecommerce operator
- Order CS-10482 received and validated
- Line and product status
- Line 2 dispatched, in transit
- Line 1 in production
- Line 3 delayed by a production issue
- Customer-facing exception note
Customer service
- Full consolidated order timeline
- All job statuses
- Packages and tracking
- Active quality exception on Line 3
- Responsible team (Production Site C)
- Customer-facing impact: one item delayed
Production manager
- Assigned facilities A, B and C
- Queue status and due dates
- Framing job B due tomorrow
- Quality failure and reprint at Site C
- Dependencies between jobs
- Rerouting and capacity activity
Print provider
- Only the reprint job assigned to this provider
- Required production assets
- Production instructions
- Due date and status controls
- The quality-control exception to act on
Restricted: unrelated customer, cost and rights-sensitive information is not shown.
Fulfilment team
- Line 2 packed into Package 1
- Shipment 1 label and collection status
- Package 2 awaiting products
- Delivery exceptions where they occur
Rights owner
- Authorised production activity for the artwork
- Product usage and edition activity
- Territory information
- Royalty status where configured
Restricted: recipient details are not shown unless required and authorised.
Finance and royalty team
- Commercial references for CS-10482
- Production and shipping costs where permitted
- Royalty records
- The exception affecting financial processing (reprint cost)
Trade customer
- Parent-order status: partially dispatched
- Order-line status and partial completion
- Tracking for the dispatched line
- Delivery progress
End customer
- Order accepted
- Partially dispatched
- Tracking for dispatched items
- Remaining item in production
- Revised delivery information where approved
Full lifecycle visibility does not mean every participant sees every field. Cloudstore presents information according to role, relationship and permission.
Access model
Illustrative role-access model
An illustrative view of how information access might differ by role. This is not the actual final Cloudstore permissions model.
| Information | Ecommerce operator | Customer service | Production provider | Fulfilment team | Rights owner | Finance | Trade customer | End customer |
|---|---|---|---|---|---|---|---|---|
| Customer details | Full access | Full access | Not shown | Limited access | Not shown | Limited access | Limited access | Limited access |
| Product information | Full access | Full access | Limited access | Limited access | Limited access | Limited access | Full access | Full access |
| Digital asset | Not shown | Not shown | Limited access | Not shown | Limited access | Not shown | Not shown | Not shown |
| Rights information | Limited access | Limited access | Status only | Not shown | Full access | Limited access | Not shown | Not shown |
| Production instructions | Limited access | Limited access | Full access | Limited access | Not shown | Not shown | Not shown | Not shown |
| Production status | Full access | Full access | Full access | Limited access | Limited access | Limited access | Status only | Status only |
| Production cost | Not shown | Limited access | Deployment dependent | Not shown | Not shown | Full access | Not shown | Not shown |
| Shipping address | Full access | Full access | Not shown | Full access | Not shown | Limited access | Limited access | Limited access |
| Tracking | Full access | Full access | Not shown | Full access | Not shown | Limited access | Full access | Status only |
| Delivery status | Full access | Full access | Status only | Full access | Not shown | Limited access | Full access | Status only |
| Royalty information | Not shown | Not shown | Not shown | Not shown | Deployment dependent | Full access | Not shown | Not shown |
| Exception details | Full access | Full access | Limited access | Limited access | Limited access | Limited access | Status only | Status only |
| Internal notes | Limited access | Full access | Limited access | Limited access | Not shown | Limited access | Not shown | Not shown |
Ecommerce operator
- Customer details
- Full access
- Product information
- Full access
- Digital asset
- Not shown
- Rights information
- Limited access
- Production instructions
- Limited access
- Production status
- Full access
- Production cost
- Not shown
- Shipping address
- Full access
- Tracking
- Full access
- Delivery status
- Full access
- Royalty information
- Not shown
- Exception details
- Full access
- Internal notes
- Limited access
Customer service
- Customer details
- Full access
- Product information
- Full access
- Digital asset
- Not shown
- Rights information
- Limited access
- Production instructions
- Limited access
- Production status
- Full access
- Production cost
- Limited access
- Shipping address
- Full access
- Tracking
- Full access
- Delivery status
- Full access
- Royalty information
- Not shown
- Exception details
- Full access
- Internal notes
- Full access
Production provider
- Customer details
- Not shown
- Product information
- Limited access
- Digital asset
- Limited access
- Rights information
- Status only
- Production instructions
- Full access
- Production status
- Full access
- Production cost
- Deployment dependent
- Shipping address
- Not shown
- Tracking
- Not shown
- Delivery status
- Status only
- Royalty information
- Not shown
- Exception details
- Limited access
- Internal notes
- Limited access
Fulfilment team
- Customer details
- Limited access
- Product information
- Limited access
- Digital asset
- Not shown
- Rights information
- Not shown
- Production instructions
- Limited access
- Production status
- Limited access
- Production cost
- Not shown
- Shipping address
- Full access
- Tracking
- Full access
- Delivery status
- Full access
- Royalty information
- Not shown
- Exception details
- Limited access
- Internal notes
- Limited access
Rights owner
- Customer details
- Not shown
- Product information
- Limited access
- Digital asset
- Limited access
- Rights information
- Full access
- Production instructions
- Not shown
- Production status
- Limited access
- Production cost
- Not shown
- Shipping address
- Not shown
- Tracking
- Not shown
- Delivery status
- Not shown
- Royalty information
- Deployment dependent
- Exception details
- Limited access
- Internal notes
- Not shown
Finance
- Customer details
- Limited access
- Product information
- Limited access
- Digital asset
- Not shown
- Rights information
- Limited access
- Production instructions
- Not shown
- Production status
- Limited access
- Production cost
- Full access
- Shipping address
- Limited access
- Tracking
- Limited access
- Delivery status
- Limited access
- Royalty information
- Full access
- Exception details
- Limited access
- Internal notes
- Limited access
Trade customer
- Customer details
- Limited access
- Product information
- Full access
- Digital asset
- Not shown
- Rights information
- Not shown
- Production instructions
- Not shown
- Production status
- Status only
- Production cost
- Not shown
- Shipping address
- Limited access
- Tracking
- Full access
- Delivery status
- Full access
- Royalty information
- Not shown
- Exception details
- Status only
- Internal notes
- Not shown
End customer
- Customer details
- Limited access
- Product information
- Full access
- Digital asset
- Not shown
- Rights information
- Not shown
- Production instructions
- Not shown
- Production status
- Status only
- Production cost
- Not shown
- Shipping address
- Limited access
- Tracking
- Status only
- Delivery status
- Status only
- Royalty information
- Not shown
- Exception details
- Status only
- Internal notes
- Not shown
Actual visibility is configured according to each deployment, organisation, workflow and data-governance requirement.
Operational timeline
See what happened, what is happening and what must happen next
An operational timeline relates the events that shaped an order. It is a traceable activity record, not a legally compliant audit trail unless formally confirmed.
- Order received
- Order validated
- Approval requested
- Approval granted
- Job created
- Job assigned
- Artwork downloaded or streamed
- Preflight completed
- Printing started
- Printing completed
- Finishing started
- Quality check completed
- Exception raised
- Job placed on hold
- Reprint created
- Package created
- Label generated
- Shipment dispatched
- Delivery exception received
- Shipment delivered
- Order completed
Each event may include, where configured:
Exception detection
Identify the conditions that require attention
Exceptions may originate across the lifecycle. Not every exception is detected automatically.
Order and customer data
- Missing customer information
- Invalid address
- Duplicate order
- Unsupported product
- Missing approval
- Payment-status hold where integrated
Content and rights
- Missing artwork
- Failed file validation
- Rights conflict
- Territory restriction
- Edition limit reached
- Asset unavailable
Production
- No eligible production destination
- Media unavailable
- Equipment unavailable
- Capacity problem
- Missed due date
- Production failure
- Finishing failure
- Quality-control failure
- Reprint requirement
Fulfilment and shipping
- Packing problem
- Missing package information
- Label-generation failure
- Carrier unavailable
- Collection missed
- Tracking not returned
- Delivery delayed
- Shipment damaged
- Failed delivery
- Return to sender
Integration
- API error
- Authentication failure
- Invalid payload
- Duplicate event
- Status-mapping failure
- Timeout
- Connected system unavailable
Exceptions may be:
Exception lifecycle
Track every exception from identification to resolution
Each exception follows a clear lifecycle and keeps its operational history.
- Exception detected
- Affected record identified
- Severity and category assigned
- Responsible team or user assigned
- Order, job or shipment status updated
- Stakeholders notified where appropriate
- Corrective action taken
- Resolution confirmed
- Operational history retained
An exception record may include
- Exception ID
- Category
- Severity
- Status
- Date and time raised
- Source
- Parent order
- Order line
- Production job
- Production facility
- Package
- Shipment
- Responsible organisation
- Assigned user or team
- Due date
- Customer impact
- Required action
- Notes
- Attachments where supported
- Resolution
- Resolution date
- Follow-up action
Illustrative exception statuses
- New
- Acknowledged
- Assigned
- Investigating
- Awaiting information
- Corrective action in progress
- Resolved
- Closed
- Reopened
- Cancelled
Ownership & escalation
Make responsibility and next action visible
Exception management can make ownership and the next required action clear. Escalation is described cautiously.
Ownership may include
- Responsible organisation
- Assigned team
- Assigned user
- Action owner
- Due date
- Priority
- Severity
- Escalation level
- Customer impact
- Production impact
- Delivery impact
- Financial impact
- Notes
- Status
- Resolution target
Possible escalation triggers
- Exception not acknowledged
- Due date approaching
- Production deadline missed
- Shipment delayed
- Delivery failed
- Rights issue unresolved
- Customer impact increased
- Repeated failure
- Manual escalation
Escalation may be driven by configured rules, connected-system events or authorised user action. Cloudstore does not claim automatic escalation unless confirmed.
Corrective action
Keep corrective action connected to the original workflow
Corrective action stays linked to the work it affects, so history is preserved.
- Corrective action should not erase the original event.
- Reprints remain linked to the original jobs.
- Replacement shipments remain linked to the original shipments.
- Rerouted jobs retain the previous assignment history.
- Cancelled items remain in the operational history.
Notifications
Communicate changes without creating disconnected information
Status and exception events may be delivered through connected channels, while respecting role and permission restrictions.
Possible channels
- Cloudstore dashboards
- Customer or partner portals
- API responses
- Webhooks
- Ecommerce updates
- CRM updates
- Email notification systems
- SMS systems where integrated
- Internal operational alerts
- Customer-service alerts
- Production-provider alerts
- Shipping or fulfilment alerts
Potential events
- Approval required
- Missing information
- Job assigned
- Production delayed
- Quality failure
- Reprint created
- Package ready
- Shipment dispatched
- Delivery delayed
- Delivery failed
- Exception assigned
- Exception escalated
- Exception resolved
Cloudstore does not claim to send every notification directly. It may display the event, trigger an integration, send the event to a connected communications system, or make it available through an API or webhook.
Customer-facing status
Translate complex operations into clear customer-facing progress
Internal status may be more detailed than the customer-visible status. Several internal stages can map to one clear customer-facing status.
“In production”
- Validated
- Jobs created
- Print queued
- Printing
- Finishing
- Quality control
- In production
“Preparing for dispatch”
- Package created
- Label requested
- Label generated
- Ready for collection
- Preparing for dispatch
- Be understandable
- Avoid exposing confidential production information
- Avoid exposing internal failures unnecessarily
- Remain accurate
- Reflect partial fulfilment where relevant
- Provide tracking when available
- Identify when customer action is required
Not all internal events should be shown to end customers.
Dashboards & queues
Help operational teams focus on what requires attention
Dashboards and work queues can help teams find the orders, jobs and exceptions that need action. Views and filters may be configured according to deployment and user role.
Possible views
- Orders requiring validation
- Orders awaiting approval
- Jobs awaiting artwork
- Jobs approaching due date
- Jobs delayed
- Jobs requiring rerouting
- Quality-control failures
- Reprints
- Packages awaiting shipping
- Shipments with no tracking
- Delivery exceptions
- Unassigned exceptions
- Overdue exceptions
- High-priority customer issues
- Rights issues
- Integration failures
Potential filters
- Organisation
- Customer
- Order
- Production facility
- Job type
- Product
- Status
- Exception category
- Severity
- Due date
- Assigned user
- Region
- Shipping provider
- Date range
Security & privacy
Maintain visibility without exposing unnecessary information
Shared visibility is designed to support controlled access. Principles can be configured according to the deployment and the customer’s security and governance requirements.
- Role-based access
- Organisation boundaries
- Least-required information
- Restricted customer data
- Restricted pricing and cost data
- Restricted rights information
- Restricted royalty information
- Restricted source assets
- Controlled production access
- Permission-based notes
- User authentication
- Session control
- Operational history
- Data retention
- Data deletion and export where applicable
Cloudstore does not claim formal certification, regulatory compliance, zero-trust architecture or absolute data isolation unless verified. These capabilities are described as designed to support controlled access, subject to each customer’s security and governance requirements.
Connected events
Bring status events together from connected systems
Status events can be brought together from many connected systems, using sound integration principles. Not every system supports every mechanism.
Potential status sources
- Ecommerce storefront
- Web-to-print portal
- Order-management system
- Product configuration service
- Production workflow
- RIP or print system
- Print provider
- Finishing partner
- Quality-control operation
- Warehouse system
- Shipping platform
- Carrier
- Customer portal
- Finance or royalty system
Possible integration mechanisms
- REST APIs
- Webhooks
- Event callbacks
- Scheduled synchronisation
- File exchange
- Manual status update
- Approved custom connectors
Bringing events together reliably calls for:
Reporting
Turn operational events into actionable insight
Connected operational events can support a range of reporting. This page covers current operational visibility; broader historical analysis lives in Data Insight.
Reporting depends on:
Current operational visibility shows where work has reached now; historical analytics and aggregated reporting are covered by Data Insight. Not every metric is available in every deployment.
Outcomes
What connected visibility and exception management makes possible
One connected operational view
Order, job, production, fulfilment, shipment and delivery information held together.
Clear order-to-job relationships
Every job, package and shipment stays linked to its parent order and line.
Role-appropriate visibility
Stakeholders see the information relevant to their role and permissions.
Earlier identification of delays
Conditions that need attention can be surfaced for the right team.
Visible next actions
The consolidated view shows who is responsible for the next step.
Clear exception ownership
Each exception carries an assigned organisation, team or user.
Traceable corrective action
Reprints, reroutes and replacements stay connected to the original work.
Better customer-service information
Teams can answer questions from one connected operational view.
Connected production and shipping status
Production completion and delivery progress are shown together.
More complete operational reporting
Connected events can support broader operational reporting, where available.
Frequently asked questions
It means authorised stakeholders can follow connected order, production-job, package, shipment, delivery and exception information within one consolidated view, with each record kept related to its parent order. Visibility may be live or regularly updated according to each connected system.
No. Full lifecycle visibility does not mean unrestricted access. Information is presented according to each participant’s role, relationship and permissions, and sensitive fields can be restricted.
They describe different records. Order status may be derived from several related records, while job, package and shipment statuses describe their own stage. They stay distinct but connected within the consolidated view.
Yes. Different jobs can hold different statuses at the same time, and an order can show several shipment statuses at once. One completed job or delivered shipment does not imply the whole order is finished.
Partial completion and partial dispatch remain visible at order and line level, so completed and in-progress work are both shown without losing the relationship to the parent order.
It is a condition that needs attention — for example a missing asset, a quality-control failure, a delivery problem or an integration error. Exceptions stay connected to the affected order, line, job, facility, package or shipment.
An exception can carry a severity, category, responsible organisation, assigned team or user, due date and resolution status, and it is tracked from identification through to resolution with its history retained.
No. Cloudstore helps identify, assign, communicate and track exceptions. It should not be described as automatically resolving every exception; corrective action depends on the responsible team and configuration.
Reprints, replacement jobs and replacement shipments remain linked to the original records. Corrective action does not erase the original event, and rerouted jobs retain their previous assignment history.
Yes, where supported and configured. Status events may be exchanged with connected systems through APIs, webhooks, scheduled synchronisation or other approved mechanisms. Not every system supports every mechanism.
Not necessarily. Visibility may be live or regularly updated depending on each connected system, so update frequency varies by integration.
Yes. Internal status can be more detailed than the customer-facing status. Several internal stages may map to a single, clear customer-facing status such as “In production” or “Preparing for dispatch”.
Through role-based access, organisation boundaries and least-required information. Customer, pricing, cost, rights, royalty and source-asset information can be restricted according to role, permission and deployment.
An operational history, or traceable activity record, can capture status changes and exception activity. It should not automatically be described as a legally compliant audit trail unless that has been formally confirmed.
Give every authorised stakeholder the visibility needed to act
Talk to us about your stakeholder roles, status models, production partners, customer-facing tracking, exception categories, escalation requirements, integration events, operational dashboards, security and permissions, and reporting requirements.