Account and authorization
Create the customer account, complete onboarding, confirm service scope, brand/label authorization, prohibited-goods acknowledgement, privacy acceptance, and payment profile readiness.
First shipment wizard
Set up the first PrepPort workflow without a long email thread.
Use this page when a customer asks, "What do I do first?" It maps the first operating session from account setup to SKU/supplier files, QC or ASN intake, Shopify/API options, quote response, payment evidence, and customer-visible tracking.
Recommended first session
This is the default path for overseas ecommerce sellers who source inventory from suppliers and want PrepPort to inspect, prep, store, source, or fulfill orders.
Operating files
Add SKU master, supplier profile, packaging/labeling/QC standard, and any artwork or marketplace prep file. These files make every later ASN, QC, RFQ, and order faster.
Choose the first workflow
Submit the first real action: product QC inspection, inbound ASN, product sourcing RFQ, drop-shipping order, Shopify test order, CSV intake, or API/webhook setup. Customers can start manually before Shopify/API is ready.
Quote, invoice, and payment evidence
Review customer-visible quotes, accept or request revision, then submit payment evidence only when requested. Payment evidence enters staff verification before paid status, wallet credit, supplier purchase, release, or shipment.
Track status and exceptions
Use Control Tower, Connection center, Action center, Activity timeline, inventory visibility, support tickets, and webhook delivery logs instead of repeating the same question across email and WhatsApp.
Minimum fields by workflow
These are the fields that reduce staff follow-up and help the Action center show precise next steps.
| Workflow | Minimum fields | Portal path |
|---|---|---|
| QC inspection | Product name, SKU, batch/PO, inspection type, quantity/sample size, checklist, required photos, defect tolerance, supplier or ASN reference. | QC inspections |
| Inbound ASN | Supplier, tracking, ETA, destination warehouse, carton count, SKU lines, quantity, services required, FNSKU/barcode/label files, packaging notes. | Inbound to warehouse |
| Product sourcing RFQ | Product/spec link, category, target quantity, target price, destination, sales channels, sample needs, procurement need, drop-shipping plan, compliance concerns. | Product sourcing RFQ |
| Drop-shipping order | Platform, order number, recipient country/address summary, shipping service, SKU lines, quantity, packaging/insert rules, ship-by requirement. | Drop shipping orders |
| CSV intake | Template type, header row, required fields, source note, preflight result, accepted/rejected rows, and apply result for ASNs, orders, QC, sourcing, SKUs, or suppliers. | CSV intake |
| Shopify sync | .myshopify.com domain, import mode, fulfillment mode, SKU mapping, wallet/deposit rule, fallback CSV process, safe test order, and Shopify order sync cockpit status. | Shopify sync |
| API/webhooks | Server-side API key name, scopes, HTTPS webhook endpoint, subscribed events, owner contact, integration test plan. | API access |
| Control Tower | Overall health, next actions, customer/staff/external blockers, inventory, sourcing, quotes, invoices, integrations, support, and first-shipment status. | Dashboard |
| Connection center | Readiness score, Shopify status, API key status, webhook health, manual/CSV fallback, first-shipment status, and next steps. | Connection center |
Customer-safe operating rules
These rules protect both sides while keeping routine work self-service.
Use portal records first
Routine ASN, QC, RFQ, fulfillment, support ticket, quote response, invoice evidence, wallet, and Shopify/API setup should live in the portal or API, not only in WhatsApp.
Keep Shopify optional at launch
Customers can start with manual forms, CSV templates, and safe test order import. Live Shopify OAuth and webhooks start after Partner app credentials are configured.
Do not bypass payment gates
Uploaded payment evidence is not settlement. Staff verifies funds before paid status, wallet credit, supplier purchase, release, or shipment.
Start with the portal, then add Shopify/API when ready.
The first workflow should work even if the customer only has supplier details and a spreadsheet today. Shopify, API, and webhooks make the same workflow scale later.