TransfersOps Complete User Manual - U.S. English - 2026 Page 1
TRANSFERSOPS
Complete Detailed User & Operations
Manual
Plain American English - Step-by-Step - Easy to Read
For Owners, Managers, Customer Service, Prepress, Production, Shipping, and
Accounting
What this manual does: It explains not only what each major TransfersOps section is for, but also how a shop should
use it, what information to check, what can go wrong, and what should happen next.
Based on the TransfersOps Training Suite reviewed August 30, 2026.
The official tutorial currently defines five onboarding areas and the production-status lifecycle. Where the public tutorial does not expose
every screen field or button, this manual labels the added content as recommended operating practice rather than claiming an
undocumented product function.

TransfersOps Complete User Manual - U.S. English - 2026 Page 2
How to Use This Manual
This manual is written for a U.S. print-shop employee who may be using TransfersOps for the first time.
Sentences are short, technical terms are explained, and each section follows the same pattern: purpose, who
uses it, step-by-step procedure, checks before moving on, and common mistakes.
Reading conventions

Confirmed feature: a capability explicitly described in the current TransfersOps tutorial.

Recommended practice: an operating procedure included to help the shop use the system consistently. It is
not presented as an undocumented software feature.

Verify in your store: a feature that may depend on the tenant's integrations, permissions, carrier account,
payment setup, hardware, or current product version.

Hold: stop the job from moving forward until a real blocking issue is resolved.

QC: quality control - the final check that the produced item meets the shop's requirements.
Quick workflow
Step Main purpose Finish this before

1. Company Setup Establish business identity, invoice branding, and shipping
origin.
Live billing/shipping

2. Store Settings Configure carriers, payments, machines, and team members. Normal daily operations

3. Standard Order Create a complete customer production order. Sending work to production

4. Quotes & Invoices Handle estimates, fast tickets, job conversion, and billing. Final commercial workflow

5. Bills & Expenses Record supplies, film, consumables, and operating expenses. Management reporting

TransfersOps Complete User Manual - U.S. English - 2026 Page 3

1. Company Setup
Purpose
Company Setup establishes the business information TransfersOps will use as the shop's identity. The current
tutorial specifically identifies legal business details, invoice branding, and the shipping origin address.
Who should complete it?
The owner, general manager, or an administrator who knows the company's correct legal and shipping
information. This should not be delegated to a temporary operator who may guess at business details.
Step-by-step
1 Open Company Settings. Work from the company-level configuration area, not from an individual order.
2 Enter the business identity. Use the official company/shop information that should identify the business to
customers.
3 Review invoice branding. Make sure the name and branding used for billing match the shop's intended
customer-facing identity.
4 Enter the shipping origin address. This should be the location from which carrier shipments are actually
tendered when the store uses shipping.
5 Review spelling and formatting. Check business name, city, state, ZIP code, and other entered details
before saving.
6 Save the settings. After saving, reopen or review the configuration to make sure the intended values
persisted.
7 Run a business-process check. Before launch, verify that the information shown on invoices and shipping
workflows is appropriate for the company.
What to check before moving on

The company name is correct and consistent.

The origin address is the actual shipping origin.

Invoice branding is intentional.

No test/demo information remains in the live company profile.

An authorized manager has reviewed the setup.
Common mistakes

Using a personal address when the carrier should use the production location.

Leaving demo/test company data in the account.

Typing a business nickname when accounting expects the legal business identity.

Assuming that because a value saved, it is automatically correct.

TransfersOps Complete User Manual - U.S. English - 2026 Page 4
Important: Company Setup is foundational. A bad origin address can affect shipping operations, and incorrect
business information can appear in customer-facing workflows.

TransfersOps Complete User Manual - U.S. English - 2026 Page 5

2. Store Settings / Workspace Configuration
The tutorial defines Store Settings as the place to register shipping providers such as UPS/FedEx, payment
methods, machines (EPSON is shown as an example), and team members. Treat this as the operational
configuration of the shop.
2.1 Shipping Providers
Shipping-provider configuration connects the shop's fulfillment process with the carrier workflow. A carrier
appearing in configuration does not by itself prove that credentials, labels, rates, or tracking synchronization are
working.
1 Select the carrier the shop actually uses.
2 Enter or connect the required carrier account information using the application's supported configuration flow.
3 Save the configuration.
4 Create a controlled test shipment before relying on the integration for customer orders.
5 Confirm that the label information uses the correct origin address.
6 Confirm that the resulting tracking information is available where expected.
7 Only after a successful test should the carrier be considered operational for the store.
2.2 Payment Methods
Payment methods tell the workflow how the shop accepts or records payment. The tutorial confirms
payment-method configuration but does not publicly expose every possible method or synchronization rule.

Enable only methods the business actually accepts.

Define which staff members may change payment-related information.

Do not mark an order paid because a customer says payment was sent; use the actual known state supported
by the shop's process.

If payment is unresolved and production should not continue, the tutorial lists unpaid balances as a valid Hold
condition.
2.3 Machines
Register the production machines the team needs to identify in its workflow. Use short, unmistakable names such
as 'DTF Printer 1' or an approved machine identifier. Avoid duplicate names that make printer assignment
ambiguous.

One physical machine should have one clear operational identity.

Remove or update obsolete machine entries when equipment changes.

Machine assignment means the job is assigned; it does not prove the job successfully printed.

Hardware-dependent automation must be tested with the actual configured equipment.
2.4 Team Members

TransfersOps Complete User Manual - U.S. English - 2026 Page 6
Add the people who need access to the workspace. Use individual accounts whenever the platform's permission
model permits it. Shared credentials make accountability and access removal more difficult.

Give each employee only the access needed for the job.

Keep administrative privileges limited.

Disable access promptly when a person leaves or changes roles.

Review user access periodically.
Store Settings completion test

Carrier workflow tested.

Payment workflow reviewed.

Machines identifiable by operators.

Team-member access reviewed.

No old/test configuration is being treated as production configuration.

TransfersOps Complete User Manual - U.S. English - 2026 Page 7

3. Standard Order - Registering a Complete Custom Order
The current tutorial says a complete custom order records customer contact, total linear inches, carrier dispatch
preference, and payment status. The goal is to create one reliable record that production and customer service
can follow.
3.1 Before creating the order

Know which customer the job belongs to.

Have the production artwork or know that artwork is still required.

Know the intended quantity/linear-inch measurement used by the shop.

Know whether the customer expects pickup or shipping.

Know the actual payment state or mark it according to the shop's unresolved/pending process.
3.2 Step-by-step order entry
1 Start a new order. Use the standard order workflow when the job needs a complete production record.
2 Select or enter the customer. Confirm name and contact information. Avoid attaching the order to the wrong
customer with a similar name.
3 Enter production measurement. Record total linear inches according to the shop's approved calculation. Do
not estimate if the order requires an exact measurement.
4 Associate the artwork. Make sure staff can identify which file belongs to the order. If the file is missing or
unusable, do not pretend the job is production-ready.
5 Choose fulfillment. Record pickup or carrier dispatch according to the customer's order.
6 Record payment status. Use the known payment state. Do not confuse an invoice being created with
payment being received.
7 Add useful operational notes. Recommended practice: record only information that helps another employee
understand the job, exception, or customer instruction.
8 Review the order. Read back the customer, measurement, artwork, fulfillment, and payment information.
9 Submit the order to the workflow. The order can then enter the Dashboard/Queue Entry stage for
verification and assignment.
3.3 Order-entry quality check
Check Question to ask If wrong
Customer Is this definitely the correct customer? Correct before production
Artwork Is the correct file available and usable? Hold / prepress correction
Size Are the production dimensions/linear inches correct? Recalculate
Payment Is the displayed state actually known? Resolve or Hold

TransfersOps Complete User Manual - U.S. English - 2026 Page 8
Check Question to ask If wrong
Fulfillment Pickup or shipping? Correct destination/process? Correct before handoff
A production order should be understandable by the next employee without requiring a verbal explanation from the
person who created it.

TransfersOps Complete User Manual - U.S. English - 2026 Page 9

4. Express Entry, Quotes & Invoice Generation
This section handles three related but different business activities. Keeping them separate prevents a quote from
being mistaken for a live production order or an invoice from being mistaken for proof of payment.
4.1 Express Entry
The tutorial describes Express Entry as fast front-desk order ticketing. Use it when the shop needs quick intake,
but do not let speed remove the information required to produce and fulfill the job correctly.

Confirm the customer.

Capture enough production information to identify the job.

Confirm artwork availability.

Confirm fulfillment intent.

Confirm or appropriately represent payment state.

Review the ticket before it enters production.
4.2 Quotes
A Quote is a preliminary proposal. The tutorial states that it is based on linear footage and transfer count and does
not deduct shop inventory or enter the active RIP print line until approved.
1 Collect the customer's job requirements.
2 Prepare the estimate using the shop's current pricing process.
3 Review the quote for obvious quantity or measurement errors.
4 Send/present the proposal to the customer using the store's approved process.
5 Wait for approval.
6 When approved, convert the quote to a live order.
7 Before production, re-check artwork, dimensions, fulfillment, and any requirements that may have changed
since the quote was created.
4.3 Invoices
An invoice is a billing document. The tutorial's standard operational flow places final billing in Stage 04, Fulfillment
& Invoicing, and instructs the operator to generate final billing with CREATE INVOICE.

Verify the invoice belongs to the correct customer/order.

Verify billable quantities before finalizing.

Do not equate 'invoice created' with 'payment received.'

If the shop changes an invoice after production, follow the business's authorization/accounting process.

Keep the order, invoice, and payment state logically distinct.

TransfersOps Complete User Manual - U.S. English - 2026 Page 10
Quote vs. Order vs. Invoice
Record What it means Production? Payment proof?
Quote Preliminary commercial proposal No, until
approved/converted
No
Order Live operational job Yes, when released
through workflow
No
Invoice Customer billing document Not by itself No - payment must be
established separately

TransfersOps Complete User Manual - U.S. English - 2026 Page 11

5. Bills & Shop Operating Expenses
The tutorial says this area is used to track supplies, film-roll purchases, consumables, and general operating
expenses. The objective is consistent business-cost capture, not merely storing receipts.
Recommended entry procedure
1 Identify the vendor or source of the expense.
2 Identify what was purchased or paid for.
3 Use the correct expense category available in the store's accounting setup.
4 Enter the amount and relevant transaction information accurately.
5 For production materials such as film or consumables, use consistent descriptions so later reports remain
understandable.
6 Review the entry before saving.
7 Correct errors using the shop's approved process so management can understand why historical data
changed.
Examples of expenses this section may be used to track

Film rolls.

Ink and production consumables.

Packaging supplies.

General shop supplies.

Other operating expenses supported by the business's configured categories.
Management rule
A report is only as reliable as the data entered into it. If bills are entered late, duplicated, omitted, or categorized
inconsistently, management totals can be misleading even if the software is functioning correctly.

TransfersOps Complete User Manual - U.S. English - 2026 Page 12

6. Order Lifecycle & Production Status Guide
TransfersOps uses operational statuses so prepress, production, front desk, and shipping staff can understand
the job without relying on verbal handoffs. A status is a statement about the job's current condition.
Status Meaning What staff should do next
Dashboard / Queue
Entry
Live order awaiting artwork verification, preflight, or printer
assignment.
Verify files and assign line
Printing / Active RIP Order is in the RIP/film-print production stage. Print film and continue
production
UV Production Specialty UV DTF/hard-surface transfer workflow. Complete UV production,
lamination, adhesion checks
Hold Production is intentionally stopped because intervention is
needed.
Resolve the blocking issue
Ready for Pickup Job passed QC and is prepared for customer handoff. Notify/handoff according to
configured process
Shipping Order is prepared for courier fulfillment. Label, tracking, carrier
scan/transit
Cancelled Transaction/job is terminated. Refund/archive as applicable
Quote Preliminary proposal, not active production. Approve/convert to live order
Status discipline

Do not move an order forward just to clear a queue.

Do not leave a completed job in an early status if the team depends on status for customer communication.

Do not mark Ready for Pickup before the product is actually complete and has passed the shop's QC.

Do not mark Shipping merely because the customer selected shipping; shipping status should correspond to
the fulfillment stage.

When the job cannot safely proceed, use Hold rather than pretending production is active.

TransfersOps Complete User Manual - U.S. English - 2026 Page 13

7. Detailed Status Procedures
7.1 Dashboard / Queue Entry
The tutorial calls this the central intake inbox. It displays live orders waiting for artwork verification, preflight
checks, or assignment.
1 Open the incoming order.
2 Verify that the customer and order information make sense.
3 Check that required artwork is available.
4 Perform the shop's preflight checks.
5 If the job is usable, assign it to the appropriate production line/workflow.
6 If a blocking problem exists, move it to Hold and document the reason.
7.2 Printing / Active RIP
The tutorial says the order has been converted into a RIP gang sheet and is printing onto PET film through roll
printers. The public tutorial gives Epson SC-F3000 as an example; do not treat that example as the only
supported hardware.

Confirm the correct job/gang sheet is being produced.

Follow the shop's established printer/RIP procedure.

Do not use the status as proof of successful output; actual production and QC still matter.

If a production defect requires intervention, follow the shop's exception/Hold procedure.
7.3 UV Production
The tutorial designates this for UV DTF stickers, hard-surface transfers, or promotional decals using UV-cure ink
sets, white backing, and varnish lamination. The listed next action is lamination and adhesion testing.

Confirm the order is truly a UV workflow.

Follow the configured UV production process.

Complete the required lamination/adhesion check.

Do not apply ordinary DTF assumptions to UV DTF without verifying the process.
7.4 Hold
The tutorial explicitly lists low-resolution artwork under 300 DPI, incorrect sizing, missing fonts, and unpaid
balances as Hold triggers.
1 Stop the job from advancing.
2 Write a clear reason for the Hold using the shop's available note/status process.
3 Identify who can resolve it: customer, prepress, accounting, or management.
4 Contact the appropriate person.

TransfersOps Complete User Manual - U.S. English - 2026 Page 14
5 Wait for the real blocking condition to be corrected.
6 Re-check the correction.
7 Only then release the order back into the appropriate production stage.

TransfersOps Complete User Manual - U.S. English - 2026 Page 15
7.5 Ready for Pickup
The tutorial describes this as a completed transfer roll that has passed QC, been cured, trimmed, and bagged at
the front counter. It says the system can automatically trigger SMS/email pickup notifications.

Verify the job is physically complete.

Verify QC is complete.

Verify the package/order identity before placing it in the pickup area.

Use automated notification only after the store's notification configuration has been tested.

At handoff, confirm the correct order is being given to the correct customer or authorized pickup person
according to shop policy.
7.6 Shipping
The tutorial describes orders packed into mailing tubes with UPS, FedEx, or USPS labels and says tracking
numbers are automatically synchronized to the customer record.
1 Confirm the order passed QC.
2 Confirm the correct shipping destination.
3 Package the product using the shop's approved method.
4 Generate/use the carrier label through the configured workflow.
5 Verify that the tracking number exists and belongs to this shipment.
6 Verify synchronization/customer visibility before telling the customer tracking is confirmed.
7 Tender the shipment to the carrier and follow the shop's normal exception process if the carrier rejects or fails
to scan it.
7.7 Cancelled
The tutorial lists customer cancellation, failed authorizations, duplicate entries, and non-viable artwork as
examples. The listed action is refund and archive.

Confirm the cancellation is authorized.

Stop any remaining production work.

Handle refund requirements according to the actual payment state and company policy.

Archive/close the job as supported by the workflow.

Do not call a payment refunded until the refund outcome is actually confirmed.
7.8 Quote
A Quote is a proposal, not production. The tutorial explicitly says it does not deduct shop inventory or enter the
active RIP line until approved.

TransfersOps Complete User Manual - U.S. English - 2026 Page 16

8. Standard DTF Operational Flow - Start to Finish
Stage 01 - Inquiry & Intake
A customer inquiry becomes either a Quote, an Express Entry ticket, or a standard order. Choose the path that
matches the job. Do not send an unapproved quote into production.
Stage 02 - Prepress & File Preparation
The order appears on the Dashboard. Staff check the files and production information. If the artwork is damaged
or otherwise cannot proceed, the tutorial directs the operator to Hold.
Stage 03 - Active Floor Production
The job moves to Printing or UV Production. The tutorial states that an automated tracker monitors film-roll
footage and ink expenditure. Because this can depend on the actual implementation/hardware configuration, test
it in the live store before using those values as accounting-grade measurements.
Stage 04 - Fulfillment & Invoicing
After production and QC, move the order to Ready for Pickup or Shipping as appropriate. The tutorial instructs the
operator to generate final billing with CREATE INVOICE during this stage.
Example: normal pickup order
Sequence Employee action
1 Create/receive the order.
2 Verify customer, artwork, dimensions, payment state, and pickup intent.
3 Preflight the file.
4 Send the job to Printing.
5 Complete production.
6 Perform QC.
7 Prepare/bag the order.
8 Move to Ready for Pickup.
9 Generate/confirm billing as required.
10 Notify and hand off to the customer.

TransfersOps Complete User Manual - U.S. English - 2026 Page 17

9. Exception Management
A good shop workflow must explain what to do when the normal path breaks. The safest rule is to preserve the
true state instead of forcing the order forward.
Artwork problem

Place the order on Hold when the file cannot safely proceed.

Record what is wrong in clear language.

Request the corrected file or have prepress correct it when authorized.

Re-check before release.
Payment uncertainty

Do not guess that payment succeeded.

If the shop requires payment before production, use Hold until the actual state is known.

An invoice is not proof of payment.

A payment/API timeout can mean the outcome is unknown; verify before retrying or making a definitive
statement.
Shipping/tracking uncertainty

Do not invent a tracking number.

Do not tell the customer a package shipped merely because a label was requested.

Verify the label/tracking result.

If a carrier integration returns an unknown result, reconcile it before repeating an action that could create
duplicates.
Duplicate order

Verify that it is truly a duplicate before cancellation.

Determine whether either copy has already entered production or billing.

Cancel/archive only the appropriate record.

Check for duplicate payment/refund implications.

TransfersOps Complete User Manual - U.S. English - 2026 Page 18

10. Daily Procedures by Employee Role
Customer Service / Front Desk
1 Review new inquiries and orders.
2 Create quotes/orders using complete customer information.
3 Confirm pickup versus shipping.
4 Check whether artwork and payment information are sufficient for the next step.
5 Use Hold instead of promising production when something is unresolved.
6 Communicate only the order status the system and physical workflow actually support.
Prepress
1 Open orders awaiting file review.
2 Verify artwork availability and basic production readiness.
3 Check dimensions and known file requirements.
4 Send usable work to the proper production path.
5 Move unusable work to Hold and explain what must be fixed.
Production Operator
1 Work from the active production queue.
2 Confirm the correct order before printing.
3 Use the correct DTF or UV workflow.
4 Complete production and report exceptions.
5 Do not mark a job complete before actual completion/QC.
Shipping / Pickup
1 Verify the finished order.
2 Confirm the customer/fulfillment method.
3 For pickup, prepare the correct package for handoff.
4 For shipping, verify destination, label, and tracking.
5 Update the operational state according to what actually occurred.
Accounting / Management
1 Review invoices and unresolved balances.
2 Enter/review bills and operating expenses.
3 Review aging Holds and cancellations.

TransfersOps Complete User Manual - U.S. English - 2026 Page 19
4 Review user access and important configuration changes.
5 Investigate inconsistent data before using reports for business decisions.

TransfersOps Complete User Manual - U.S. English - 2026 Page 20

11. Owner & Manager Control Checklists
Opening checklist

Review new Dashboard orders.

Review orders still on Hold.

Identify jobs that must ship or be ready for pickup today.

Review any carrier/payment/integration exceptions.

Confirm production staff understand priority work.
Midday checklist

Check whether early jobs moved to the expected production stages.

Resolve customer/prepress Holds.

Review jobs waiting for shipping information.

Look for orders whose system status does not match the physical shop floor.
Closing checklist

Review unfinished active production.

Review Ready for Pickup orders.

Review shipments and tracking exceptions.

Review cancellations/refunds that still need action.

Confirm important bills/expenses were captured.

Leave clear statuses/notes for the next shift or next business day.
Weekly checklist

Review aging orders and Holds.

Identify repeated artwork/prepress problems.

Review carrier and notification failures.

Review user access.

Review expense consistency.

Check whether staff are using statuses consistently.

Train on the highest-frequency workflow error.

TransfersOps Complete User Manual - U.S. English - 2026 Page 21

12. Charlie AI - Product, Pricing & Future Operations
Assistant
The current TransfersOps tutorial presents Charlie AI as a Live Product & Pricing Advisor. The public greeting
says Charlie can help with pricing plans, DTF features, integrations, supported hardware, shipping, and the
14-day free demo.
12.1 Public product-advisor behavior

Answer product questions using confirmed TransfersOps information.

Explain the free-demo process accurately.

Do not invent plan pricing or supported integrations.

When hardware or integration support is configuration-dependent, say that it should be verified.

Do not claim access to a customer's live account unless Charlie is actually connected and authorized.
12.2 Future operational Charlie
For an operational assistant that can look up orders or perform actions, the recommended architecture is a
controlled API between Charlie and TransfersOps. Charlie should not receive unrestricted database authority.
Action type Example Required control
Read Look up order status Authenticated API + tenant/user authorization
Read Daily totals Authorized company scope + defined calculation
Write Change order status Validation + authorization + audit trail
Write Add order note Tenant scope + user permission
Write Send customer email Approved recipient/content + audit/result state
External Create shipping action Idempotency/reconciliation for uncertain results
Multi-tenant security: Charlie must never trust a company/tenant ID supplied by a customer as proof of access.
The server must establish and authorize tenant context.
12.3 Charlie's truth rules

Confirmed: evidence establishes the fact.

Supported / likely: evidence points to it, but it is not yet proven.

Unknown / unverified: Charlie does not have enough evidence and should say so.

A timeout does not prove failure.

A queued action does not prove execution.

An invoice does not prove payment.

A shipping label request does not prove carrier acceptance.

TransfersOps Complete User Manual - U.S. English - 2026 Page 22

A saved setting does not prove an integration works.

TransfersOps Complete User Manual - U.S. English - 2026 Page 23

13. Free Demo Onboarding
The current tutorial advertises a 14-day full-platform trial without payment information. The demo form shown on
the page asks for Company / Shop Name, Desired Subdomain, Full Name, Email Address, Password, and
Password Confirmation.
Demo setup procedure
1 Choose the company/shop name for the demo.
2 Choose the desired subdomain shown in the demo flow.
3 Enter the administrator's full name.
4 Enter a valid administrator email address.
5 Create and confirm a password.
6 Create the free demo account.
7 After entering the workspace, complete Company Setup first.
8 Continue through Store Settings before testing normal orders.
9 Use test data intentionally and do not confuse demo transactions with live customer transactions.
Security recommendation
Use a unique password and keep administrator credentials limited to the person responsible for the account. Do not
share the administrator login with production-floor users if individual access is available.

TransfersOps Complete User Manual - U.S. English - 2026 Page 24

14. Employee Training Scenarios
Scenario A - Low-resolution artwork
Situation: An order is paid, but the file is below the shop's required resolution and cannot safely proceed.
Correct response: Put the order on Hold, identify the file problem, contact the customer/prepress resource, and
release it only after the corrected file is verified.
Scenario B - Quote approved
Situation: Customer says yes to the quote.
Correct response: Convert the quote into a live order and re-check production requirements. Approval does not
mean the original quote was already printing.
Scenario C - Printed but not QC'd
Situation: The film printed, but the job has not completed QC.
Correct response: Do not mark Ready for Pickup yet.
Scenario D - Carrier API uncertainty
Situation: The shipping action times out.
Correct response: Treat the outcome as unknown until verified. Do not automatically repeat an operation that
might create a duplicate label/charge.
Scenario E - Wrong tenant request
Situation: A user asks Charlie to look up an order under another company ID.
Correct response: Do not switch company context based solely on the supplied ID. Authorization must come
from the server-side tenant/user relationship.
Scenario F - Customer says 'I paid'
Situation: Customer says payment was made, but the system does not yet confirm it.
Correct response: Do not mark paid based only on the statement. Follow the shop's payment verification
process.

TransfersOps Complete User Manual - U.S. English - 2026 Page 25

15. Plain-English Glossary
Term Plain-English meaning
Dashboard / Queue The place where live incoming work waits for review or assignment.
Preflight Checking the file/order before production.
RIP Software/process that prepares artwork for the printer.
Gang sheet Multiple designs arranged together for efficient printing.
Linear inches A production-length measurement used by the shop/order workflow.
Hold Stop the job because something must be fixed or confirmed.
QC Quality control - verify the finished work is acceptable.
Quote An estimate/proposal before it becomes a live job.
Invoice A bill sent to the customer.
Carrier Shipping company such as UPS, FedEx, or USPS.
Tracking number Carrier identifier used to follow a shipment.
Tenant One company/shop account inside a multi-company SaaS platform.
API A controlled software interface that lets systems exchange data/actions.
Idempotency Design that prevents repeated attempts from creating duplicate logical side effects.

TransfersOps Complete User Manual - U.S. English - 2026 Page 26

16. Feature Verification Matrix
This page separates what the current public tutorial explicitly says from items that still depend on each store's live
configuration.
Explicitly described in the current tutorial

Five-step training suite: Company Setup, Store Settings, Standard Order, Quotes & Invoices, Bills & Expenses.

Company legal/business details, invoice branding, and shipping origin configuration.

Shipping providers, payment methods, machines, and team-member configuration.

Standard order data including customer contact, total linear inches, carrier dispatch preference, and payment
status.

Express Entry, quote conversion, and invoice generation.

Bills/expense tracking for supplies, film rolls, consumables, and general operating expenses.

Dashboard, Printing, UV Production, Hold, Ready for Pickup, Shipping, Cancelled, and Quote statuses.

Hold examples including under-300-DPI artwork, incorrect sizing, missing fonts, and unpaid balances.

Quote does not enter active RIP production until approved.

14-day full-platform demo without payment information.

Charlie AI presented as a Live Product & Pricing Advisor.
Verify in the actual tenant before relying on it

Exact carrier credential/label/tracking behavior.

Exact automatic SMS/email notification behavior.

Exact film-footage and ink-expenditure tracking behavior.

Exact supported hardware and machine integrations.

Exact team-member roles and permissions.

Exact payment-provider synchronization.

Any Charlie access to live order/customer data.

Any Charlie write action such as status change, email, shipping, or billing.
This manual intentionally does not invent hidden fields, buttons, permissions, or integration behavior that the public
tutorial does not expose.

TransfersOps Complete User Manual - U.S. English - 2026 Page 27

17. New-Shop Launch Checklist
Done Launch item
[ ] Company identity reviewed
[ ] Invoice branding reviewed
[ ] Shipping origin verified
[ ] Carrier integration tested
[ ] Payment workflow tested
[ ] Machines registered and clearly named
[ ] Team-member access reviewed
[ ] Standard test order completed
[ ] Hold and release tested
[ ] Quote converted to order
[ ] Invoice workflow tested
[ ] Bill/expense entry tested
[ ] Ready for Pickup workflow tested
[ ] Shipping/tracking workflow tested
[ ] Notifications tested if enabled
[ ] Management reviewed the complete workflow

18. Final Operating Rules

The order status must match reality.

Do not guess payment, shipping, or production outcomes.

Use Hold when a real blocker exists.

A Quote is not a live production order.

An Invoice is not proof of payment.

A label request is not proof of shipment.

A configured integration is not proven until it is tested.

Customer data and company/tenant boundaries must be authorized server-side.

Charlie should say 'I cannot verify that yet' rather than invent an answer.

TransfersOps Complete User Manual - U.S. English - 2026 Page 28

Good data entry is part of production quality.
Official reference
TransfersOps Training Suite - Interactive Onboarding & Training Center
https://transfersops.com/tutorial
Manual edition prepared from the tutorial version reviewed August 30, 2026.