Product Overview
DeliveryDesk Fulfillment Sync ("Fulfillment Sync") is a Commerce7 app for wineries and DTC shippers that eliminates one of the most repetitive jobs in order operations: copying tracking numbers into Commerce7 one order at a time.
You upload the CSV or Excel shipment file you already receive from your warehouse or fulfillment house. Fulfillment Sync reads the file, matches each row to a Commerce7 order, checks the order's current fulfillment state, and shows you exactly what it proposes to do. Only after you approve does it write tracking numbers, carrier, ship date, and fulfillment status back to Commerce7. You control whether Commerce7 sends the customer shipping notification for each shipment.
What it's for
- Bulk tracking import. Twenty orders or two thousand: validate an entire fulfillment file at once and fix only the exceptions.
- Flexible files. CSV and Excel up to 25 MB, with automatic column mapping and no mandatory template. Common heading variants are recognized automatically, and you can save a named mapping profile per fulfillment house.
- Existing-fulfillment awareness. Orders already fulfilled (for example, weather holds fulfilled without tracking) are detected and handled with clear Add, Replace, or Skip choices. Nothing is silently overwritten.
- Duplicate protection. Uploading the same file twice is safe. Shipments already recorded are skipped, with no duplicate fulfillment records and no duplicate customer notifications.
- Notification control. A per-row (and default) flag decides whether Commerce7 sends the shipping notification for each shipment.
- Row-level audit history. Every import, decision, and write is recorded, so you always know what changed and who approved it.
Fulfillment Sync runs inside your Commerce7 admin as an embedded page. There is no separate website and no second password to remember.
Getting Started
- Install the app for your Commerce7 tenant from the Commerce7 App Store, or accept the install your account has been granted.
- Open Fulfillment Sync from its menu entry in your Commerce7 admin. The embedded page loads and you are signed in automatically with your Commerce7 account, with no signup and no password.
- Upload your first file. Use the shipment CSV or Excel export you already receive from your warehouse or fulfillment house.
- Confirm the column mapping. Adjust any columns the automatic detection missed, and optionally save the mapping as a profile for future imports from the same source.
- Review the preview, then commit. Check the proposed actions, override anything you want handled differently, and approve the import. Your tracking data is now written to Commerce7.
Import history, saved mapping profiles, and default settings (ship-date default, notification default, and how to handle fulfillments that already exist without tracking) are all available in the app's settings and history pages.
How It Works: End-to-End Flow
Every import follows a two-phase model. Analyze is read-only, so nothing is written. Commit happens only after your approval. Nothing changes in Commerce7 until you approve the import.
- Upload. Drag and drop your CSV or Excel shipment file (up to 25 MB). No special template is required.
- Confirm columns. Fulfillment Sync auto-detects which column is the order number, tracking number, carrier, ship date, and notify flag. Adjust any misses with dropdowns, and optionally save the mapping as a named profile for next time.
- Analysis. A background job checks every row against your live Commerce7 data: matching orders, reading each order's current fulfillment state, and normalizing carriers, tracking numbers, and dates, with live progress as it goes.
- Preview. You see a summary (Total, Ready, Already Imported, Needs Review, Errors) and a per-order table showing each order's current state and the proposed action: Create, Add, Replace, Skip, or Needs Review. You can override any row before committing; destructive replacements always require a second explicit confirmation.
- Commit. Approved writes are executed against Commerce7 one row at a time, with automatic rollback safety for replacements and resumable progress if anything is interrupted.
- Results. A final report shows created, added, replaced, skipped, and failed counts, with a downloadable error file (your original row data plus the reason and a suggested fix) so you can correct and re-upload quickly.
How each order is decided
| Situation found in Commerce7 | Proposed action |
|---|---|
| Order unfulfilled, valid tracking in file | Create the fulfillment with tracking, carrier, ship date, and notification flag |
| Tracking already on the order | Skip (idempotent: no duplicate record, no duplicate notification) |
| Fulfilled but no tracking (e.g. weather hold) | Replace offered. The old fulfillment state is saved, removed, and recreated with the real shipment data (requires your confirmation; fully logged) |
| Existing tracking differs from the file | Needs review. You choose Add as new package, Replace, or Skip; nothing is written until you choose |
| Partially fulfilled order | Needs review (never auto-replaced) |
| Order not found or bad row | Error on that row only; all other rows continue |
Billing
Fulfillment Sync is a flat $12.50/month subscription for Commerce7 App Store installs, billed through your Commerce7 subscription, with no separate invoice and no separate payment to us. There is no free trial on App Store installs; billing starts when you install, per Commerce7's own subscription mechanics. You can cancel at any time from your Commerce7 admin by uninstalling the app.
Accounts onboarded outside the Commerce7 App Store are billed separately by DeliveryDesk via Stripe Checkout subscription billing. No card data ever passes through Fulfillment Sync's servers.
Frequently Asked Questions
Do I need a special file template?
No. Common CSV and Excel column headings are mapped automatically, and you can correct any column with a dropdown and save the mapping for reuse.
What if an order is already fulfilled?
Fulfillment Sync checks the order's actual fulfillment state first, then offers to skip it, add tracking, or replace the existing fulfillment (with your confirmation). It never silently overwrites.
What happens if I upload the same file twice?
Shipments already recorded are detected and skipped, so there are no duplicate fulfillment records and no duplicate customer notifications.
Can I control customer shipping notifications?
Yes, per row, per import default, and per account default. When the file has no email column, your chosen default applies.
What if a row has a problem?
Only that row fails; every other row continues. A downloadable error file gives your original data, the reason, and a suggested fix.
Support & Contact
Fulfillment Sync is built and operated by DeliveryDesk.ai.
| Support | shipments@deliverydesk.ai |
|---|
Please include your Commerce7 tenant name and, if relevant, the import date/time so we can locate the exact import in the audit history.