Cloudstore Platform
Shipping & Fulfilment Integration
Keep production, dispatch, tracking and delivery connected to every order. Cloudstore connects completed production jobs with packing, shipping and fulfilment systems. Dispatch requests, package information, labels, tracking references and delivery events remain associated with the relevant order, jobs and recipients, giving authorised stakeholders a consolidated view from production completion through final delivery.
Shipping is not a passive final box in the workflow. Cloudstore treats it as a two-way operational connection with shipping-management systems, carrier APIs, courier, freight and warehouse systems, fulfilment centres, tracking services and returns systems — carrying dispatch data out and bringing status back, where supported and configured.
Cloudstore connects production and Order Management with shipping and fulfilment systems, keeping packages, shipments, tracking events, delivery exceptions and final outcomes associated with one consolidated order view. Cloudstore is not itself a carrier, courier, warehouse operator or physical fulfilment provider unless explicitly confirmed.
Shipping & Fulfilment Integration
A Platform capability covering order-to-shipment relationships, package records, dispatch instructions, shipping-system connections, label and tracking exchange, delivery events, shipment exceptions, shared visibility, and APIs and status data.
Print Fulfilment
A service and operating-model topic covering in-house and partner fulfilment, distributed and regional production, direct-to-customer delivery and fulfilment-network operation.
From production to delivery
Production does not end when printing is complete
Several operational stages may follow printing before an order reaches the customer.
Throughout these stages, Cloudstore preserves the relationship between:
- Parent order
- Order lines
- Production jobs
- Finishing operations
- Packages
- Shipments
- Tracking events
- Delivery outcome
Shipment hierarchy
One order can create multiple packages and shipments
An illustrative view of how one consolidated order relates to its lines, jobs, packages and shipments.
Parent order and production jobs
- Parent order CS-10482
- Order line 1
- Print job A
- Framing job B
- Order line 2
- Canvas job C
- Order line 3
- Poster job D
- Order line 1
Completed work is packed
- Package 1 Framed print & poster
- Package 2 Canvas wrap
Packages become shipments with their own tracking
- Package 1 Shipment 1 Tracking reference 1
- Package 2 Shipment 2 Tracking reference 2
Both shipments remain connected to one consolidated parent order.
- One order may contain multiple order lines.
- Different jobs may complete at different times.
- Products may be packed together or separately.
- One order may have multiple packages.
- One order may have multiple shipments.
- Shipments may originate from different locations.
- A customer may receive partial deliveries.
- Cloudstore maintains the consolidated parent-order relationship.
- Not every order requires multiple shipments.
Explore the workflow
Follow an illustrative order from production to delivery
Move through the stages of a sample order to see how packages, shipments, tracking and stakeholder views stay connected. Everything shown is illustrative.
Illustrative workflow
A sample order shown to illustrate how production, packing, shipping and delivery stay connected.
- Order
- CS-10482
- Order lines
- 3
- Completed jobs
- 4
- Production sites
- 2
- Packages
- 2
- Shipments
- 2
- Tracking
- 2
- Consolidated order views
- 1
Order overview
Order CS-10482 contains three order lines that produce four completed jobs across two production origins, resulting in two packages and two shipments with separate tracking references — all held within one consolidated parent-order view.
Production Site A completes the framed print and poster (Package 1); Regional Production Site B completes the canvas wrap (Package 2). Each ships separately, yet both stay connected to the same order.
Production completion
| Job | Order line | Production origin | Illustrative status |
|---|---|---|---|
| Print job A | Order line 1 | Production Site A | Complete |
| Framing job B | Order line 1 | Production Site A | Complete |
| Canvas job C | Order line 2 | Regional Production Site B | Complete |
| Poster job D | Order line 3 | Production Site A | Complete |
Illustrative origin names. No real production partners are named.
Packages
Package 1 — Production Site A
Framed fine-art print and poster
Package 2 — Regional Production Site B
Canvas wrap
A package is not the same as a production job. One package may contain products from several jobs, and a package record stays connected to its original order.
Shipping requests
For each package, Cloudstore may send a connected shipping system the information needed to prepare a shipment, where supported and configured:
Only the information required by the connected shipping workflow is exchanged. Not every deployment supplies every field.
Carrier responses
The connected shipping system may return information that stays associated with the package, shipment and parent order:
Cloudstore does not generate every label itself. Labels may be returned by a connected shipping platform or fulfilment partner and printed at the relevant location.
Tracking events
- Awaiting shipment
- Label created
- Collected
- In transit
- Out for delivery
- Delivered
- Awaiting shipment
- Label created
- Collected
- In transit
- At local depot
- Out for delivery
Shipment status is distinct from order and production-job status. One parent order may show several shipment statuses at once; a delivered shipment does not imply the whole order is complete.
Delivery exceptions
An exception on one shipment stays connected to the affected package, shipment and parent order without making delivered shipments appear unfinished.
- In transit
- Delivery exception
- Customer service notified
- Replacement or redelivery action
- Resolution recorded
Cloudstore surfaces the exception so the right team can act; it does not claim to resolve carrier exceptions automatically.
Stakeholder views
This demonstration illustrates a potential permissions model. Actual access is defined by each Cloudstore deployment.
Ecommerce operator
- Dispatch readiness
- Shipment creation
- Tracking number
- Delivery progress
- Customer-facing exceptions
- Delivery completion
Customer service
- Consolidated order view
- Production completion
- Package records
- Partial dispatch
- Tracking
- Delivery exceptions
- Returns
- Replacement shipments
Fulfilment operator
- Jobs awaiting packing
- Packing instructions
- Package requirements
- Label status
- Collection status
- Dispatch confirmation
- Shipping exceptions requiring action
Production manager
- Jobs awaiting packing
- Production completion
- Package requirements
- Dispatch confirmation
- Shipping exceptions requiring action
- Fulfilment-centre performance, according to permissions
Shipping team
- Dispatch queue
- Package information
- Service selection
- Carrier response
- Manifest status
- Collection status
- Delivery exceptions
Trade customer
- Order-level progress
- Shipment count
- Partial dispatch
- Tracking references
- Delivery progress
End customer
- Preparing for dispatch
- Dispatched
- Tracking
- Out for delivery
- Delivered
- Delivery issue
Finance and reporting
- Shipping cost
- Surcharge
- Service used
- Delivery performance
- Exception frequency
- Return or replacement activity
Illustrative production-to-delivery timeline
- Production job completed
- Released by quality control
- Packing instructions applied
- Package created
- Shipping request submitted
- Service selected
- Label returned
- Ready for collection
- Carrier collection
- In transit
- Out for delivery
- Delivered
- Delivery event returned to Cloudstore
- Consolidated order status updated
Exception branch
- In transit
- Delivery exception
- Customer service notified
- Replacement or redelivery action
- Resolution recorded
Stages are illustrative and require alignment with the actual Cloudstore shipping-status model. Status is conveyed with text and icons, not colour alone. Any motion is a subtle, pausable highlight that stops when off screen, when the tab is hidden, when paused, or when reduced motion is requested.
Connected systems
Connect the systems responsible for dispatch and delivery
Cloudstore can connect categories of shipping and fulfilment systems, where supported and configured.
Existing supported integrations
Connections already available within Cloudstore deployments.
Configurable integrations
Connections that can be enabled and configured for a deployment.
API-enabled possibilities
Connections that may be built against available interfaces.
Custom integrations
Connections developed for specific operational requirements.
Planned integrations
Connections under consideration but not yet available.
No specific third-party brands or logos are shown. Cloudstore does not imply connections to every carrier or shipping platform.
Data exchange
Two-way data exchange with shipping systems
Cloudstore sends the information required to dispatch a shipment and brings shipping and delivery events back into the order lifecycle.
Sent to shipping systems
- Order reference
- Job references
- Package reference
- Recipient name
- Delivery address
- Contact details where required
- Delivery instructions
- Package quantity
- Package dimensions
- Package weight
- Product description
- Declared value where required
- Requested shipping service
- Delivery priority
- Dispatch location
- Dispatch date
- Label request
- Customs description
- Commodity information
- Country of origin
- Tariff or classification data where available
- Tax or duty information where applicable
- Return address
- Customer-facing reference
Returned by shipping systems
- Available delivery services
- Shipping rates where supported
- Selected carrier
- Selected service
- Label
- Tracking number
- Collection reference
- Collection status
- Manifest status
- Dispatch confirmation
- In-transit status
- Estimated delivery
- Out-for-delivery status
- Delivery confirmation
- Delivery date and time
- Delivery exception
- Failed-delivery event
- Return-to-sender event
- Return tracking
- Proof-of-delivery information where available
- Shipping cost
- Surcharges where available
Returned information remains associated with:
Only the information required by the connected shipping workflow is exchanged. Not every deployment supplies or receives every field; provider-dependent capabilities apply where supported and configured.
Service selection
Apply delivery requirements consistently
Shipping-service selection may consider configured information, and may be made in several ways depending on the deployment.
Selection may consider
- Destination
- Delivery deadline
- Product type
- Package dimensions
- Package weight
- Product value
- Fragility
- Framed or glazed products
- Oversized items
- Shipping restrictions
- Customer-selected service
- Trade-account rules
- Carrier availability
- Regional service coverage
- Production origin
- Shipping price
- Delivery service level
- Customs requirements
- Manual override
Possible operating models
- Customer selects a service
- Ecommerce platform supplies a service
- Cloudstore applies configured shipping rules
- Fulfilment location selects a service
- External shipping platform selects a service
- Operator manually overrides the service
Shipping-service decisions may be made by Cloudstore, a connected commerce system, a fulfilment partner or an external shipping platform according to the deployment. Cloudstore does not claim automatic rate shopping or optimisation unless confirmed.
Packages
Keep package records connected to the products and jobs they contain
Packages are distinct from production jobs, and each package record stays connected to its original order.
- A package is not the same as a production job.
- One package may contain products from several jobs.
- One job may contribute to one or more packages where the product model requires it.
- Package records should remain connected to the original order.
Where packing relies on operator input, Cloudstore describes it as such rather than overstating automated packing.
Labels and dispatch
Connect shipping preparation to operational status
A package moves through a possible preparation and dispatch lifecycle.
- Package ready
- Shipping request created
- Service selected
- Label requested
- Label returned
- Label printed
- Package manifested
- Ready for collection
- Collected
- Dispatched
Labels may be:
- Generated by a connected shipping platform
- Returned through an API
- Generated by a fulfilment partner
- Associated with the package and shipment
- Printed at the relevant fulfilment location
Cloudstore does not claim to generate every label directly. A shipping-label failure should create a visible exception rather than silently losing the shipment.
Tracking
Follow each shipment without losing the complete order view
Illustrative shipment statuses, subject to alignment with the actual Cloudstore shipping-status model.
- Awaiting shipment
- Service selected
- Label requested
- Label created
- Ready for collection
- Collected
- In transit
- At local depot
- Out for delivery
- Delivered
- Delivery exception
- Failed delivery
- Returned
- Cancelled
- Shipment status is distinct from order status.
- Shipment status is distinct from production-job status.
- A parent order may have several shipment statuses simultaneously.
- Partial delivery should remain visible.
- A delivered shipment should not imply that all jobs or shipments are complete.
- Status frequency depends on the connected shipping system.
- Customer-facing wording may be simpler than internal operational wording.
Cloudstore provides live or regularly updated tracking visibility rather than claiming every event is instant. Status names are illustrative.
Multi-origin
Coordinate fulfilment across multiple production locations
An order may be produced and dispatched across more than one location.
Cloudstore should not imply a single shipment when an order is only partially fulfilled. The consolidated parent-order view is retained across origins, packages and shipments.
Cross-border
Support cross-border shipping information where required
Connected workflows may require additional information for international delivery, depending on the provider, destination and deployment.
Availability depends on the selected shipping provider, destination and deployment. Cloudstore does not provide legal, customs, tax or trade-compliance advice and does not claim automatic customs compliance; businesses remain responsible for approving their customs and commercial information.
Delivery exceptions
Keep delivery problems connected to the affected shipment and order
When delivery problems occur, they stay connected to the shipment, package, products, jobs and parent order.
The relationship is preserved from exception to resolution:
- Delivery exception
- Shipment
- Package
- Affected products
- Production jobs
- Parent order
- Responsible stakeholder
- Resolution history
Possible actions include:
- Assign an exception owner
- Request address correction
- Contact the fulfilment location
- Contact the carrier through the appropriate system
- Change shipping service where possible
- Issue a replacement shipment
- Create a reprint where required
- Update customer-facing status
- Record the resolution
- Retain the history
Surfacing an exception helps the right team act on it; Cloudstore does not claim that carrier exceptions are resolved automatically.
Returns and replacements
Preserve the relationship between the original shipment and its resolution
Returns, replacements and re-dispatch stay linked to the original order, job, package and shipment.
- Original order
- Original production job
- Original package
- Original shipment
- Delivery or quality exception
- Reprint or replacement
- Replacement package
- Replacement shipment
Replacement activity should not erase the original history. Exact return-management capabilities require confirmation and are described cautiously.
Shared visibility
Give each authorised stakeholder the shipping information relevant to their role
Different stakeholders see the shipping information relevant to their role and permissions.
Ecommerce operator
- Dispatch readiness
- Shipment creation
- Tracking number
- Delivery progress
- Customer-facing exceptions
- Delivery completion
Customer service
- Consolidated order view
- Production completion
- Package records
- Partial dispatch
- Tracking
- Delivery exceptions
- Returns
- Replacement shipments
Fulfilment operator
- Jobs awaiting packing
- Packing instructions
- Package requirements
- Label status
- Collection status
- Dispatch confirmation
- Shipping exceptions requiring action
Production manager
- Jobs awaiting packing
- Production completion
- Package requirements
- Dispatch confirmation
- Shipping exceptions requiring action
- Fulfilment-centre performance, according to permissions
Shipping team
- Dispatch queue
- Package information
- Service selection
- Carrier response
- Manifest status
- Collection status
- Delivery exceptions
Trade customer
- Order-level progress
- Shipment count
- Partial dispatch
- Tracking references
- Delivery progress
End customer
- Preparing for dispatch
- Dispatched
- Tracking
- Out for delivery
- Delivered
- Delivery issue
Finance and reporting
- Shipping cost
- Surcharge
- Service used
- Delivery performance
- Exception frequency
- Return or replacement activity
Shared shipping visibility does not mean unrestricted access. Cloudstore presents package, tracking, cost and delivery information according to each participant’s role and permissions. Private customer, cost and recipient information is not exposed in the end-customer view.
Notifications
Use shipping events to keep connected systems and people informed
Shipping events may be shared with connected systems, which may be responsible for customer communication.
Possible channels
- API responses
- Webhooks
- Ecommerce status updates
- Customer portal updates
- Internal dashboards
- Email notification systems
- SMS notification systems where integrated
- CRM updates
- Customer-service alerts
- Operational exception alerts
Potential events
- Package ready
- Label generated
- Dispatch confirmed
- Tracking available
- Collected
- Delayed
- Out for delivery
- Delivered
- Delivery exception
- Returned
Cloudstore does not claim to send every notification directly. It may supply an event to another connected system responsible for customer communication.
APIs and integration
Connect shipping data through controlled interfaces
Shipping data can be connected through a range of integration mechanisms, following sound integration principles.
Integration mechanisms
- REST APIs
- Webhooks
- Scheduled synchronisation
- File exchange
- Partner connectors
- Custom integration
- Manual import or export where applicable
Integration principles
- Authentication
- Authorisation
- Idempotent requests
- Duplicate-event handling
- Event timestamps
- Provider references
- Order and job references
- Error responses
- Retry behaviour
- Status mapping
- Audit or operational history
- Version control
- Sandbox or test environments where supported
Cloudstore does not claim specific API functionality that has not been implemented or confirmed.
Reporting
Turn delivery activity into operational insight
Connected shipping and delivery data can support a range of operational reporting, where available.
Reporting depends on:
Not every metric is available in every deployment. Reporting depends on connected systems, data supplied, permissions, configuration and retention policy.
Outcomes
Business outcomes
Connecting production completion to final delivery can support clearer operations and customer service.
- Shipping connected to the parent order
- Clear package and shipment relationships
- Support for partial dispatch
- Consolidated multi-origin visibility
- Connected labels and tracking
- Faster identification of delivery exceptions
- Better customer-service information
- Role-based shipping visibility
- Traceable returns and replacements
- More complete delivery reporting
Frequently asked questions
It is the platform capability that connects completed production jobs with packing, shipping and delivery systems, keeping packages, shipments, tracking events and delivery outcomes associated with one consolidated order view, where supported and configured.
No. Cloudstore is not a carrier, courier, warehouse operator or physical fulfilment provider unless explicitly confirmed for a deployment. It connects production and Order Management with the shipping and fulfilment systems that perform those activities.
Yes. A single order can result in multiple packages and shipments, each with its own tracking reference, while remaining connected to one consolidated parent order. Not every order requires multiple shipments.
Yes. Different products may be produced at different locations, so an order can be dispatched as separate shipments from more than one origin, with partial dispatch represented and the consolidated order view maintained.
Labels and tracking references returned by a connected shipping system are associated with the relevant package, shipment, order lines, production jobs and parent order. Cloudstore does not claim to generate every label itself.
Where supported and configured, connected shipping systems can return tracking and delivery events that update the order view. This provides live or regularly updated visibility rather than guaranteed real-time events on every integration.
When one part of an order ships before another, the dispatched shipment is shown as dispatched while the remaining work continues. A delivered shipment does not imply that all jobs or shipments are complete.
An exception stays connected to the affected shipment, package and parent order, with an owner and resolution history. Surfacing an exception helps the right team act; Cloudstore does not claim to resolve carrier exceptions automatically.
Where supported, returns, replacements and re-dispatch can be linked back to the original order, job, package and shipment so that replacement activity does not erase the original history. Exact return-management capabilities require confirmation.
Yes. Package, tracking, cost and delivery information is presented according to each participant’s role and permissions. Shared visibility does not mean unrestricted access, and private recipient or cost data is not exposed in customer-facing views.
No. Connectivity depends on supported integrations, shipping-management platforms, carrier APIs, deployment configuration and any custom integration requirements. We do not imply universal carrier support.
Where integrated, shipping events such as dispatch and tracking can be supplied to a connected commerce system responsible for updating the storefront and notifying the customer.
Connect production completion to final delivery
Talk to us about your fulfilment operations, shipping platforms, carrier connections, package rules, multi-site production, tracking requirements, stakeholder visibility, exception handling, international delivery and returns.