🚀 Storefront Admin Problem Solvers 🚀

Read our handy storefront styling tips and tricks!

Job Statuses in Shared Print Operations: What Do They Mean?

 

Shared Print Operations uses a set of job statuses to track the lifecycle of a print order. These statuses indicate where a job currently sits within the workflow, from creation and approval through production, fulfilment, and integration with external systems such as MIS platforms.

Understanding these statuses helps administrators and operators determine what stage a job is at and whether any action is required.


 

Order Creation & Initial Processing

Nothing

The job exists but no processing has started yet.

Example:
A job record is created but the system has not yet begun processing the order.


Creating

The system is currently generating the job and preparing it for processing.

Example:
A user completes checkout and the system begins creating the job entry and preparing associated data.


InBasket

The job is currently in the user’s basket but has not been submitted.

Example:
A customer adds a product to their basket but has not yet placed the order.


Ordered

The order has been successfully submitted and entered the production workflow.

Example:
A user completes checkout and the job is now ready to move through output generation and production.


FutureOrder

The order has been placed but is scheduled to be processed at a later time.

Example:
A recurring order scheduled to run next month.


UnapprovedOrder

The order has been created but still requires approval before production can begin.

Example:
A corporate ordering workflow where a manager must approve the order before printing.


 

Output Generation

 

These statuses track the creation of print-ready files.


OutputCreationStarted

The system has started generating the output files.

Example:
A PDF proof or print-ready artwork file is being generated after an order is placed.


OutputCreated

Output files have been successfully generated.

Example:
The final print-ready PDF has been created and is ready to be sent to production.


OutputCreationFailed

An error occurred during output generation.

Example:
A missing font or artwork issue prevents the system from generating the print-ready file.


ExternalOutputRequested

An external system has requested output generation.

Example:
A third-party production system requests the job’s output files.


ExternalOutputJobClosed

The external output request has completed.

Example:
An external system finishes processing the requested output files.


 

Production Workflow

 

These statuses represent stages of the print production process.


InProduction

The job is currently being printed or produced.

Example:
A batch of brochures is actively printing on a production machine.


InArtworking

Artwork preparation is taking place.

Example:
A designer is adjusting the artwork or preparing files before printing.


InReprographics

Files are being prepared for print reproduction.

Example:
Colour adjustments or file preparation are being completed before sending the job to the printer.


InFinishing

Post-print finishing processes are being applied.

Example:
A printed booklet is being bound or trimmed.


InPacking

The printed items are being packed for shipping.

Example:
Finished products are placed into boxes and labelled.


Printed

The job has completed the printing stage.

Example:
A run of posters has finished printing and is ready for packing or finishing.


InHotFolder

The job has been copied to a hot folder for automated print processing.

Example:
A print server automatically detects the job and begins processing it.


CopyToHotFolderFailed

The job failed to copy to the hot folder.

Example:
A network issue prevents the job file from reaching the printer’s hot folder.


CopyToHotFolderSkipped

The job was configured not to use a hot folder.

Example:
The job is handled through a different production workflow.


 

Shipping & Fulfilment


Shipped

The job has been dispatched to the customer.

Example:
A courier collects the printed materials and tracking information is generated.


ReadyForCollection

The order is ready for customer pickup.

Example:
A local customer collects printed materials from the print shop.


 

Approval & Validation

 

These statuses relate to order review and validation workflows.


AwaitingApproval

The order requires approval before continuing.

Example:
A marketing manager must approve a branded document before printing.


Approved

The order has been approved.

Example:
A manager approves a batch of business card orders.


PartiallyApproved

Only part of the order has been approved.

Example:
Two products in a multi-product order are approved while one remains pending.


Rejected

The order has been rejected.

Example:
Artwork does not meet brand guidelines and the order is rejected.


AwaitingProof

The order is waiting for proof approval.

Example:
A customer must approve a proof before production begins.


AwaitingData

Required information is missing.

Example:
A customer has not uploaded required artwork files.


AwaitingParts

The job is waiting for additional components.

Example:
A promotional pack requires multiple items that are not yet available.


RecreationRequested

A new version of the output has been requested.

Example:
Artwork changes require regeneration of the print file.


Verified

The job has passed verification checks.

Example:
All required assets and data are confirmed to be correct.


ValidationFinished

Validation processes have completed successfully.


ValidationFailed

Validation checks failed.

Example:
Artwork dimensions do not match product requirements.


 

Communication Statuses

 

These statuses relate to notifications sent to customers or administrators.


SentEmail

An email notification has been successfully sent.

Example:
An order confirmation email is sent to the customer.


SentEmailFailed

An email notification was attempted but failed to send.

Example:
An order confirmation email fails to send because the mail server is temporarily unavailable.


EmailBounced

The email was delivered to the recipient's mail server but was rejected or bounced.

Example:
A shipment notification email is sent but the recipient's email address no longer exists.


EmailBouncedAndPrintJobCreated

An email bounced and the system created a print job as an alternative communication method.

Example:
A billing statement email fails and the system generates a physical print job to send the document by post.


NoEmailBounceActionRequired

An email bounced but no further action is required.

Example:
A notification email fails, but the system determines the notification is non-critical and no additional action is needed.


SmsDispatching

The system is currently attempting to send an SMS notification.

Example:
A text message is being sent to notify a customer that their order has shipped.


SmsDispatched

The SMS notification has been successfully sent.

Example:
A customer receives a text message confirming their print order is ready for collection.


 

MIS Integration Statuses (with examples)

MisNotified

The system has notified the external MIS system about the job.

Example:
A new order is sent to the MIS so it can be scheduled for production.


MisFailed

Communication with the MIS system failed.

Example:
The system attempts to send job details to the MIS but the MIS server is unavailable.


MisNotificationRetrigger

The system is retrying sending the job notification to the MIS.

Example:
A previous attempt to notify the MIS failed, so the system retries the notification.


MisAdditionalActionRequired

The MIS system requires additional steps before processing can continue.

Example:
The MIS system requires additional job information or manual confirmation before scheduling production.


MisManifested

The job has been registered or manifested within the MIS system.

Example:
The MIS creates a production ticket for the job.


MisOrderProcessed

The order has been successfully processed by the MIS system.

Example:
The MIS schedules the job in the production queue.


MisAssetsOk

All required assets have been successfully delivered to the MIS.

Example:
Artwork files and production data are successfully transferred to the MIS system.


MisAssetsFailed

Asset delivery to the MIS system failed.

Example:
Artwork files cannot be uploaded to the MIS due to a network error.


MisPartiallyFailed

Some MIS actions succeeded while others failed.

Example:
Artwork files were transferred successfully, but the job creation failed in the MIS.


 

Additional Workflow Statuses 

TemplateProductCreated

A template product has been successfully generated.

Example:
The system automatically creates a reusable template product based on an existing design.


TemplateProductCreationFailed

The system attempted to create a template product but failed.

Example:
The template generation process fails due to missing design assets.


ActionRun

An automated system action has been executed.

Example:
A scheduled automation updates the job status or triggers an integration process.


MisNotificationRetrigger

A previously failed MIS notification has been triggered again.

Example:
The system retries sending job data to the MIS after a temporary failure.


CustomStatus

A custom workflow status defined by the system or integration.

Example:
A print provider creates a custom status such as “Awaiting Courier Pickup”.


CustomStatusHidden

A custom status that exists in the workflow but is hidden from standard user views.

Example:
An internal processing status used by system integrations but not visible to operators.


MisAdditionalActionRequired

Additional actions are required by the MIS before the job can proceed.

Example:
The MIS flags the job for manual review before scheduling production.


ReadyForCollection

The order is ready to be collected by the customer.

Example:
Printed posters are finished and waiting at the print shop reception desk.


MisManifested

The job has been officially recorded or manifested in the MIS.

Example:
The MIS assigns the job to a specific production batch.


CopyToHotFolderFailed

The system attempted to copy files to a printer hot folder but the operation failed.

Example:
The network printer share is unavailable when the system tries to copy the print file.


Blocked

The job cannot proceed because of a dependency or issue.

Example:
Production is paused because artwork approval has not yet been received.


ArtworkUploaded

Artwork files have been uploaded to the job.

Example:
A customer uploads a logo file required for printing business cards.


CopyToHotFolderSkipped

The hot folder step was intentionally skipped.

Example:
The job is sent to production through a different workflow instead of using a hot folder.


MisOrderProcessed

The MIS system has completed processing the order.

Example:
The job has been scheduled and allocated to a production machine.


MisAssetsOk

Assets required by the MIS have been successfully delivered.

Example:
Artwork files and print instructions are transferred to the MIS.


MisAssetsFailed

The asset transfer to the MIS failed.

Example:
An artwork file upload fails due to a server timeout.


PartiallyApproved

Some parts of the job have been approved while others are still awaiting approval.

Example:
Two items in a multi-product order are approved while another still requires review.


JobDataDeleted

Job-related data has been removed from the system.

Example:
Temporary processing data is deleted after job completion.


ValidationFailed

Validation checks did not pass.

Example:
The uploaded artwork file is missing required print marks.


ValidationFinished

All validation checks have completed successfully.

Example:
The system confirms the artwork size and resolution are correct.


MisPartiallyFailed

Some MIS operations completed successfully while others failed.

Example:
The job was created in the MIS, but artwork transfer failed.


ApprovalJobUpdated

The approval status of the job has been updated.

Example:
A manager approves an order that was previously awaiting approval.


OutputDelete

Generated output files for the job have been removed.

Example:
Old output files are deleted after a job is recreated with updated artwork.

What Does the Clean-up Status mean in Shared Print Operations?

 

This article explains what the CleanUp status does in the SPO (Shared Print Operations) view and how it behaves after an order is shipped, completed or cancelled.

CleanUp means the system has cleared the order’s working folder because the order is complete or cancelled. The cleanup is automatic and is triggered when the order is shipped; it happens within seconds and cannot be changed.

Files are cleared from the working folder to manage storage, but users can still place re-orders. If you need a job reopened (for example to retrieve files or re-run outputs), a support agent can reopen the job on request. In this ticket the customer confirmed that filtering SPO by the completed/shipped order status also shows jobs that have been moved to CleanUp.

Use cases

  • An order is shipped, completed or cancelled and the system clears the working folder and marks jobs as CleanUp.

  • You need to place a re-order after files were cleared; re-ordering is still possible.

  • You need files or the job reopened after CleanUp; request a support agent to reopen the job.

  • You want to confirm which jobs were cleaned up by filtering SPO by order status (shipped/complete).

Key settings in Infigo

  • Order status (Shipped / Complete / Cancelled / CleanUp): affects whether the system clears the order’s working folder and changes job availability; location in UI: SPO order status filter / search by status.

Step by step guide

1. Mark the order as shipped, complete or cancelled in SPO. The system will automatically trigger the CleanUp process when the order is shipped.
2. The CleanUp process clears the order’s working folder and the status changes to CleanUp. This happens within seconds and cannot be changed by users.
3. After CleanUp, the Download Output button is no longer available for that job in SPO. If you need outputs or files restored, contact a support agent and request that the job be reopened.
4. To find jobs that have been cleaned up in SPO, set the order status filter to shipped or complete and review the listed jobs. 

For additional guidance, please visit the Infigo Academy or contact our Customer Support team.

How Can I Correct an Incorrect Refund Amount on an Order?

 

If an incorrect refund amount is recorded against an order in Infigo, you may notice that the order totals display a different refund amount than what was actually processed through the payment provider.

This can happen if a refund value is entered incorrectly when marking the order as refunded.

Currently, refund values recorded on an order cannot be reset or edited after they have been applied.

This article explains what happens when an incorrect refund is recorded and what options are available.


What Happens When a Refund Is Applied

 

When an order is marked as partially refunded or fully refunded, Infigo records the refund amount in the order financials and updates the order notes.

For example:

  • An order total may be £100

  • A refund of £20 is recorded

  • The order is marked as Partially Refunded

  • The refund value becomes part of the order’s financial record

Once saved, this value is locked within the order totals.


Why the Refund Amount Cannot Be Edited

 

The refund amount becomes part of the order’s financial history once it has been recorded.

For this reason:

  • The refund value cannot be reset

  • The refund value cannot be amended

  • There is no “undo” option for refund totals

This behaviour ensures the integrity of the order's financial records.


Attempting to Edit the Refund via "Edit Order Totals"

 

In the order admin panel, you may see the option:

 
Edit Order Totals
 

However, this option does not allow refund values to be edited or corrected once they have been applied.

The refund amount recorded during the refund process remains fixed.


Recommended Workaround

 

If an incorrect refund amount is recorded, the recommended approach is to document the correction in the order notes.

For example:

  • Add an internal order note explaining the correct refund amount

  • Record the actual refund processed through the payment provider

  • Include any relevant reference information

This ensures that anyone reviewing the order understands the discrepancy between the recorded refund and the actual refund issued.


Example Scenario

 

Example situation:

  1. An order total is £50

  2. A refund is mistakenly recorded as £20

  3. The correct refund issued through the payment provider is £10

Because the refund amount cannot be changed after it has been recorded, the order will still display a £20 refund in the financial totals.

In this case, you should add an order note explaining that the correct refund was £10.


Summary

 

If an incorrect refund amount is recorded on an order:

  • The refund value cannot be reset or edited

  • The refund amount becomes part of the order’s financial history

  • The best workaround is to add an explanatory note to the order

This helps maintain accurate documentation of what occurred while preserving the order’s financial record.

How Can I Export the Customer List from My Storefront?

 

This article explains how to export a complete list of customers from your storefront using the reporting tool available in the Infigo platform.

Follow the simple step-by-step guide to navigate to the reporting section, download the Customer Report, and select your preferred date range and file format.

These instructions ensure you can routinely access customer data for analysis, marketing, or record keeping without having to repeatedly ask for support.

Use cases

  • Export customer data for targeted marketing campaigns.
  • Perform data analysis for business insights.
  • Maintain an up-to-date customer database for record keeping.

Key settings in Infigo

  • Insights > Reports: Access this section via the main navigation menu.

Step-by-step guide

  1. Log in to your Infigo account and navigate to the Insights > Reports section.
  2. Select the Customer Report from the list of available reports.
  3. Choose your desired date range and file format for the export.
  4. Download the report to obtain the complete list of customers.

Related links

For additional guidance, head over to the Infigo Academy or contact our Customer Support team.

How Do I Add or Edit Purchase Order (PO) Number in Admin Order Details?

 

You can add or edit a PO number to an order after it’s been placed, or clear it if needed. The action button automatically adapts to the state of the field:

  • If the order has no PO number: you’ll see Add PO.

  • If the order has a PO number: you’ll see Edit.

This is useful when a PO wasn’t captured during checkout (for example, if the selected payment method doesn’t require a PO number) but needs to be recorded later for invoicing or procurement.


Use Cases

  • A customer provides a PO number after checkout (e.g., via email) and you need to record it on the order.

  • The selected payment method didn’t require a PO number, but finance needs one for billing.

  • The PO number was entered with a typo and needs correction.

  • The PO requirement changed after order placement, and you need to add or remove it for compliance.


Step-by-Step Implementation Guide

Add a PO number to an order that doesn’t have one

  1. In Admin, go to Sales > Orders and open the order.

  2. In Order Details, find the Purchase Order (PO) Number section.

  3. Click Add PO

  4. Enter the PO number.

  5. Click Save.

    • The PO number is stored on the order.

    • The button changes from Add PO to Edit.

Edit an existing PO number

  1. Open the order in Sales > Orders.

  2. In the PO Number section, click Edit.

  3. Update the PO number.

  4. Click Save.

    • The updated PO number is saved.

Remove a PO number (return to “Add PO” state)

  1. Open the order and click Edit in the PO Number section.

  2. Clear the PO number field.

  3. Click Save.

    • The PO number is removed.

    • The button reverts to Add PO.

Incomplete

Can’t find what you need?

Ask our Infigo Support Team for help..

🔎
Loading…
    Select a Problem Solver