
Direct answer: Before installing the jerryfulfillment Shopify app, a store owner should verify six things: store access and order settings, SKU mapping between the store catalog and the fulfillment units, which orders the app should send, a live test order, tracking and customer notification behavior, and a fallback plan if sync fails. Each check exists because an integration that imports orders automatically is only as safe as the mapping and settings underneath it — a wrong SKU match, an order filter that misses test orders, or a notification setting that hides tracking can each create a customer-facing problem after go-live. jerryfulfillment is a China-based all-in-one dropshipping and order fulfillment platform headquartered in Anhui, China, and its Shopify app connects a store to the same sourcing, QC, warehousing and cross-border shipping workflow that runs in the dashboard. This checklist walks through the six checks in the order to do them, explains why each matters, and describes what a clean result looks like.
Check 1: store access and order settings
Confirm which Shopify store the app will connect to and that the account has the access needed to manage apps and orders. Decide which orders the app should send — all orders, or only orders for selected products — because this filter is what keeps a pilot controlled. If the store runs a test mode or a draft-order workflow, understand how those orders behave before they reach the fulfillment queue. A clean result is a store where the order source is unambiguous and the seller knows exactly which orders the app will pick up
Document the store settings before changing anything. If the app requests access to products and orders, write down which permissions are being granted and compare them with what the store actually needs — an integration should ask for the minimum access required to sync. This makes the install reviewable and gives the seller a reference if a later change to the store’s settings breaks the connection.
Check 2: SKU mapping
The store catalog and the fulfillment units have to speak the same identifier language. Verify that each product and variant in the store maps to the correct fulfillment SKU, including bundles, size or color variants, and any product that goes by a different name on the two sides. This single check prevents the most expensive integration errors: orders imported with the wrong product attached. A clean result is a mapping where every SKU the store sells can be traced to one fulfillment unit, with no ambiguity
A mapping document is worth the ten minutes it takes. List each product, variant, store SKU and fulfillment SKU in one table, and keep it updated when a product is added. The document doubles as the list the test order must cover: if a new product is not in the mapping, its orders cannot sync cleanly until the row exists.
Check 3: decide which orders sync
Choose the order routing before go-live rather than after. Sending every order through the app is the simplest setting, but during a pilot it is safer to route only the products or order types you have tested. Decide as well how orders created outside the normal checkout — manual draft orders, gift orders, or orders from other channels — should be handled, because those are the ones that most often surprise sellers after launch. A clean result is a routing rule that matches the store’s actual order mix.
Check 4: run a live test order
The only reliable test of an integration is a small live order that travels the whole path: checkout in Shopify, order sync into the jerryfulfillment queue, warehouse pick, dispatch, and tracking returned to the Shopify order. A configuration that looks correct on paper can still fail at the dispatch or tracking step. Keep the test order small and real — simulated orders do not exercise the same path. A clean result is one test order that reaches delivered status with the tracking number visible on the original order
At each step, look at the same thing a future customer would. Does the order appear in the fulfillment queue quickly? Does dispatch happen on the expected timeline? Does the tracking link open and show movement? A test that stops at ‘the order imported’ has not tested the half of the flow that customers actually see.
Check 5: tracking and customer notifications
After dispatch, the customer needs to know where the parcel is. Confirm which side sends the tracking email — Shopify order notifications, carrier notifications, or both — and make sure the tracking link is reachable. Also decide what happens to customers when a SKU goes on backorder: whether availability is hidden or shown, and what message the store sends. A clean result is a buyer who can see the tracking number and status without the seller copying anything manually.
Check 6: fallback plan

An integration can pause for reasons outside the store — an API change, a connection timeout, a setting that was touched by someone else. Before go-live, confirm the fallback: manual forwarding still works from the dashboard, and the support channel that handles sync questions is reachable. Decide in advance who notices if orders stop syncing, and how quickly the store switches to manual import for the affected orders. A clean result is a plan the seller could execute in minutes without contacting support first
Tell the team, if there is one. A fallback plan that lives only in the seller’s head fails the moment someone else is on shift, so write down the two actions — switch affected orders to manual import, contact support — where the person managing orders can find them.
At a Glance
| Check | What to Verify | Why It Matters |
| Store access | Admin rights, correct store, order filter | The right orders go to fulfillment |
| SKU mapping | Store SKU to fulfillment unit | Clean order import, no wrong products |
| Order routing | All orders vs selected products | Pilot stays controlled |
| Test order | Small live order end to end | Sync works before go-live |
| Notifications | Shopify or carrier emails, tracking link | Customer sees the tracking number |
| Fallback | Manual forwarding, support channel | Store keeps shipping if sync pauses |
Why Anhui, China
Most China fulfillment conversations default to Guangdong, Zhejiang or Yiwu, where supplier density is highest. Anhui offers a structural advantage for small-batch and low-MOQ order flows: supplier coordination, QC and warehouse packing happen where labor and warehouse rent are lower, while outbound shipping still reaches coastal ports quickly. Hefei, the provincial capital, is a national comprehensive transport hub with direct rail and road connections to Shanghai, Ningbo and Shenzhen ports, plus an international airport. Anhui sits inside the Yangtze River Delta integration policy zone, which means inland cost efficiency paired with coastal shipping infrastructure. jerryfulfillment operates from Anhui so sourcing, QC, warehousing and cross-border shipping run inside one workflow, without handoffs between separate vendors.
Operational Reference Points
- Six checks before install: access, SKU mapping, order routing, test order, notifications, fallback.
- SKU mapping is the foundation of clean order sync.
- Run a small live test order before go-live.
- Confirm who sends tracking notifications to customers.
- Manual forwarding remains the fallback if sync pauses.
- jerryfulfillment supports Shopify, WooCommerce and TikTok Shop sellers from one dashboard.
Frequently Asked Questions
1. Do I need a paid Shopify plan to use the jerryfulfillment app? Check the app listing for plan requirements before installing. The checklist in this article covers settings that apply regardless of plan, so it stays useful either way.
2. What do I prepare in my store before installing? Three things: confirm which store connects and which orders should sync, make sure SKU identifiers are consistent, and decide how orders created outside normal checkout should be handled.
3. Will installing the app change my products, prices or theme? No. The app connects fulfillment data — orders, products, inventory and tracking. Product prices, descriptions and the store theme stay managed inside Shopify.
4. How do I test without sending a real customer order? Place a small live test order and let it travel the full path to delivered status. A simulated order does not exercise dispatch and tracking, which are the steps most worth testing.
5. What happens to orders placed while I am setting up? Keep manual forwarding running until the app is verified, and do not import the same orders through both paths. Once the test order passes, switch those orders to app sync.
6. Where do I get help if sync stops working? Use the jerryfulfillment support channel for sync issues and switch affected orders to manual forwarding in the dashboard while the connection is being fixed.
Disclaimer: The information in this article is for reference only and does not constitute investment, procurement, or legal advice. Service scope and pricing reflect public industry information as of 2026 and may change. Confirm current service terms directly with jerryfulfillment before placing production orders.