Fulfilment rule design
Zones, product restrictions, packing assumptions, pickup and local delivery options.
Shipping Integration
Connect checkout promises to fulfilment reality.
Scope local and instant delivery, Canada-wide carrier shipping through merchant-owned ClickShip/Freightcom accounts, and Jaranova Delivery OS for dispatch, drivers, tracking and proof. Merchant charges and Jaranova service-package responsibilities are kept clear.
Connected retail operations
From Your Store Shelves to Your Customer's Doorstep.
Online shoppingIn-store ordering POS connection planned
- 01Customer shopping
Find products online or in store.
- 02Checkout
Choose an eligible fulfilment method.
- 03Order management
Validate stock, address and order status.
- 04Fulfilment
Pick, pack and prepare the handoff.
- 05Ship or deliver
Use the agreed carrier or local fleet.
- 06Track & confirm
Review tracking and delivery evidence.
A proposed operating journey. WooCommerce, carrier and POS connections are validated per merchant before activation.
What we can scope together
Know what each workstream involves.
The following workstreams inform your proposal. The agreed deliverable list defines what is included; they are not an automatic package bundle.
Shipping connector review
Carrier coverage, account access, labels, rates and tracking requirements checked against supported interfaces.
Order handoff
Map paid orders, shipment states, tracking information and customer notification ownership.
Exception testing
Failed rates, unavailable addresses, cancelled orders, returns and duplicate requests tested safely.
A visual workflow
From requirements to a reviewed rollout.
- Map fulfilment rules
- Verify carrier/connector support
- Build and test handoffs
- Train staff and review rollout
Workflow illustration. Application connections and automation are verified separately before activation.
Three parts of your fulfilment planChoose the journey.
Choose the journey.
Keep control of the operation.
Connect store orders with the right delivery method, shipping account and operating tools.
Reach nearby customers.
Scope local delivery around pickup readiness, service areas, capacity and customer expectations. Instant or scheduled services depend on the supported provider and location.
Coverage & service level confirmed per storeShip through your own account.
Use merchant-owned ClickShip/Freightcom accounts for eligible carrier services. ClickShip documents WooCommerce order/product sync, checkout rates, label creation and tracking.
Provider capability documented · Store setup requiredCoordinate dispatch and drivers.
The public platform presents merchant workspaces, dispatch, driver assignments, tracking and proof of delivery. Verify the current build and merchant connection before a live rollout.
Explore Delivery OS ↗Match the method to the promise
Nearby now. Scheduled later. Shipped farther.
| Method | Ideal use case | Merchant responsibilities | Availability |
|---|---|---|---|
| Local / instant delivery | Nearby retail orders needing a prompt handoff. | Prepare the order; confirm address, coverage, driver/provider capacity and any handling requirements. | Quote and service-area review; no universal delivery time promised. |
| Scheduled delivery | Agreed delivery windows or planned store routes. | Set cutoffs, pickup readiness, capacity and customer availability. | Where supported by the selected provider and current operating build. |
| Canada-wide shipping | Carrier-eligible parcels beyond the local delivery area. | Own and fund the shipping account; supply accurate weights/dimensions, package goods, book handoff and handle exceptions. | Carrier coverage, service terms and product eligibility apply. |
Clear account ownershipYour account.
Your account.
Your shipping charges.
Merchants fund ClickShip/Freightcom labels and carrier charges through their own accounts. Applicable Jaranova integration, maintenance and support services are covered by the agreed service package. Jaranova does not pay merchants’ shipping charges.
Connection status
- WooCommerce → ClickShip: provider-documented; merchant setup and testing required.
- WooCommerce → Delivery OS: publicly described; current merchant integration needs acceptance testing.
- Jaranova POS → fulfilment: planned; supported operations and data ownership must be verified.
- Trexity integration: planned, not activated or verified as live.
Provider references: ClickShip WooCommerce capabilities · ClickShip shipping & billing · Freightcom account responsibilities. No carrier rate or paid provider plan is included without agreement.
Integration planning
Start with your existing systems.
- WooCommerce shipping rules where relevant
- Existing authorized carrier account/API
- Delivery OS integration pending verification
- CRM notification mapping after acceptance tests
Access, compatibility, provider terms and acceptance testing determine what can be connected. No new subscription is assumed.
Who this helps
Choose by business need.
- Stores shipping physical goods
- Grocery businesses offering local fulfilment
- Businesses replacing manual order handoffs
Implementation & commercial scope
Know what happens before you commit.
Plan & timing
Review goals, users, content, data and system access. Agree a dated milestone plan after discovery. Complexity, dependencies and review turnaround determine the schedule; no unverified fixed delivery time is promised.
Quote & approval
Receive a proposal with deliverables, exclusions, responsibilities and acceptance criteria. Provider fees, licenses, media spend and ongoing support are separated where applicable.
Compare Launch, Grow, Scale & custom scope ↗Build & support
Review on an isolated environment, test the agreed scenarios and approve the release separately. Handover, maintenance hours, response expectations and change requests are defined in the support agreement.
Before we talkUseful answers.
Useful answers.
Clear next steps.
Questions specific to Shipping Integration.
Which carriers can you integrate?
We assess your preferred carrier and connector documentation, account eligibility and destination coverage. No universal carrier support is claimed.
Is postage included in your service fee?
No postage, carrier subscription or transaction charge is assumed. Those costs are identified by the applicable provider.
Can customers see live rates?
Live rates depend on the account, connector, packing data and API support. They require representative test scenarios.
Can orders go directly to Delivery OS?
This is a requested integration requiring verification. We must validate the order contract, authentication and retry behaviour before promising activation.
How do you avoid duplicate shipments?
Use a stable order/shipment identity, idempotent requests where supported and reconciliation before retrying failed work.
What happens when a shipping request fails?
The agreed workflow defines a visible exception queue or manual fallback rather than silently treating the order as fulfilled.
Can you support pickup or local delivery zones?
Those rules can be scoped based on operating hours, capacity, address coverage and available extensions.
What ongoing support is required?
Carrier/API changes, plugin updates and fulfilment exceptions need an agreed monitoring and maintenance responsibility.
Continue your journey