First shipment wizard

Set up the first PrepPort workflow without a long email thread.

Start with your account, add your products and choose the service you need. Track receiving, inspections, quotes and shipments in one place.

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.

Your account and permissions

Create your account and choose the services you need. Confirm your details and any product or brand permissions required for that work. Standard inbound warehouse work does not require an advance deposit.

Operating files

Start with a product name and quantity. The portal creates an internal product code if you do not have one. Add supplier, label, packing or inspection files only when the chosen work needs them.

Choose the first workflow

Submit the first real action: product a product inspection, incoming shipment, sourcing request or customer shipment. Add CSV or a verified store connection when you need it. You can use forms or CSV import before connecting a store.

Accrue charges, then settle before dispatch

Receiving, inspection, prep, and storage can proceed under the accepted quote without inbound payment. When inventory is ready to leave, review the final dispatch invoice and pay through the approved channel. Uploaded payment evidence is not settlement; finance verifies cleared funds before release.

Track status and exceptions

Use Overview, 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

Have these details ready for the service you choose. We will ask for additional information only when it is needed.

WorkflowMinimum fieldsPortal path
QC inspectionProduct name, quantity and inspection criteria. Add supplier location/contact, timing and batch references when relevant; these must be confirmed before any on-site work.QC inspections
Inbound ASNProduct name and quantity. Supplier, your reference and SKU are optional in the portal; a missing SKU gets your own internal code. Add carrier, tracking and cartons when known. API and CSV imports still need their specified identifiers.Inbound to warehouse
Product sourcing RFQProduct/spec link, category, target quantity, target price, destination, sales channels, sample needs, procurement need, drop-shipping plan, compliance concerns.Product sourcing RFQ
Drop-shipping orderSelect saved products and quantities, recipient name, street, city, destination country and shipping service. An order reference is generated if left blank. Add the destination postal code where required. Optional extras and deadlines need confirmation.Drop shipping orders
CSV intakeTemplate 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, dispatch-invoice rule, fallback CSV process, safe test order, and Shopify order sync cockpit status.Shopify sync
API/webhooksServer-side API key name, scopes, HTTPS webhook endpoint, subscribed events, owner contact, integration test plan.API access
OverviewOverall health, next actions, customer/staff/external blockers, inventory, sourcing, quotes, invoices, integrations, support, and first-shipment status.Dashboard
Connection centerReadiness score, Shopify status, API key status, webhook health, manual/CSV fallback, first-shipment status, and next steps.Connection center

Before work starts

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

You can start with forms or CSV templates. The workspace preview is read-only; do not put demonstration records into your live account. Live Shopify OAuth and webhooks start after Partner app credentials are configured.

Payment is due at the right stage

Inbound receiving and standard prep do not need prepayment. Supplier purchases and third-party costs may. Every outbound release still requires verified settlement or approved credit.

Start with the portal, then add Shopify/API when ready.

Start with a product name and quantity. No supplier profile or spreadsheet is required for a basic portal inbound request. Shopify, API, and webhooks make the same workflow scale later.

Open portal setup