Cross-border commerce

Bring stock, money and listings
back to the same business event.

Know what changed, who owns it and what is still unresolved.

Connect product facts, inventory, platform responses and payment events. NovaPilot gives supply chain, operations, service and finance verifiable facts, options and accountable next steps.

For marketplace sellers and independent commerce teams. Configured by market, channel and business rules. These are solution designs, not customer outcome claims.

AN INDUSTRY SOLUTION IN 95 SECONDS

The stock arrived. Why is the promotion still at risk?

Commerce leaders · Operations, supply chain and finance teams

Mandarin audio · Chinese / English captions · Full industry solution

The operating problem

Stock exists in the system, but availability before a campaign is uncertain. Reversed reimbursements are hard to match to recovered stock, while separate refunds and replacements can duplicate remedies.

How specialists respond

Inventory specialists distinguish in-transit, received and sellable stock, then compare waiting, transfers and replenishment. Launch roles follow evidence, reviews and page changes. Settlement and order specialists connect financial, stock and remedy records.

Outputs and business value

Receive a sellable-stock gap analysis, response options, launch tasks, reconciliation exceptions and order recommendations to reduce blind spots, rework and duplicate-remedy risk.

An illustrative solution, not a customer performance claim. Data requires authorization and important actions remain owner-approved. Validate outcomes against your systems, evidence and acceptance samples.

Read the full narration

0:05 The stock has arrived, but the promotion still cannot start. The system says stock is available. How much can you actually sell?

0:14 The reimbursement was reversed. Did the stock return? Customer service is preparing a refund, but the warehouse already sent a replacement. Teams keep checking, yet the issue stays unclear.

0:26 NovaPilot is your commerce AI expert team. See stock, money and handling progress clearly, and prepare the next business move.

0:35 Inventory specialists separate in-transit, received and sellable stock. Compare waiting, transfers and replenishment against campaign dates to see gaps and trade-offs earlier.

0:47 After documents are submitted, who supplies missing evidence and follows the review? When products change, which pages are affected? Digital roles follow through so launch blockers stay visible.

1:00 Settlement specialists check reimbursements, reversals and inventory. For order exceptions, check delivery, replacements and refunds before preparing recommendations, reducing duplicate-remedy risk.

1:12 Check the original evidence whenever needed. Data use requires authorization. Important actions need your approval.

1:21 Choose a stock or order exception and rehearse it with us. We configure the solution and validate agreed outcomes. NovaPilot: fewer blind spots for your team and greater confidence in your business.

START WITH THE OUTCOME YOU OWN

One business event. Not four disconnected investigations.

Service and finance

Before the next refund, replacement or dispute, see which money and stock actions have already happened.

See the relevant playbook

ONE CHANGE. MORE THAN ONE CONSEQUENCE.

What still has to happen after a shipment is closed?

Receipt recordsSellable statusCampaign and supply decisionApproval and verification

The product retains these states separately. The specialist prepares options, owners decide purchases or campaign changes, and controlled tools execute and verify the result. One green state does not close the whole job.

OPERATIONAL PLAYBOOKS

Make the issue reviewable, actionable and testable.

Start with the issue you recognize. Expand its inputs, handling, human decisions and exception outcomes. These are evidence-informed solution designs, not customer outcome claims.

01 · Supply chain × Operations

The stock arrived. Why is the promotion still at risk?

Delivery, shipment closure, internal processing and sellable stock are different facts.

Explore the work, exceptions and acceptance
Where the work breaks
A campaign is planned against total stock while some units remain unavailable. The gap appears late, forcing an expedite or a plan change.
Evidence to bring
SKU/location mapping, sellable and reserved balances, inbound and receipt events, refresh times, campaign dates and a demand range.
How the product helps
The inventory specialist separates stock states and flags stale evidence, then compares release, transfer, replenishment and campaign-change options.
Who makes the important decision
Supply chain verifies release expectations; operations decides campaign trade-offs. Authorized owners approve purchasing, transfers and additional spend.
Branches to rehearse
On-time release: track it. Delay: recalculate the gap. Stale data: verify first. Over-budget expedite: escalate. Rejection: retain the risk and alternatives.
What the team receives
A dated availability gap, alternatives, evidence timestamps, owner tasks and decisions.
What to measure
Warning lead time, preparation effort, evidence completeness and release-date error. No promise of zero stockouts.
Delivery dependencies and boundaries
Delivery depends on stock definitions and timing across systems. Availability planning and marketplace-fee calculations use separate definitions.

Evidence: Seller report: closed shipment, unavailable stock

02 · Product × Compliance × Operations

The documents are submitted. The stock is still waiting.

Upload is not approval. A pending review still needs an owner and a next step.

Explore the work, exceptions and acceptance
Where the work breaks
Evidence is spread across suppliers and teams. Old versions circulate while requests and pending reviews lose ownership, but purchasing and launch plans continue.
Evidence to bring
Marketplace and item identifiers, original evidence and scope, versions and validity, review requests, platform states and affected stock and plans.
How the product helps
The review application links gaps and conflicts to platform requests. A digital role follows evidence owners and shows the exposure to launch plans and inventory capital.
Who makes the important decision
Product and compliance owners verify evidence and applicability. Operations adjusts launch timing; authorized people approve submissions.
Branches to rehearse
Complete evidence: review. Model mismatch: pause the item. Additional request: assign a specific task. Extended review: owners decide follow-up and inventory action.
What the team receives
An item evidence package, version comparison, missing-document list, exposure and next owner.
What to measure
Response time, first-review completeness, unowned pending cases and inventory exposure. Submissions are not approvals.
Delivery dependencies and boundaries
Map the evidence repository to platform requests. AI does not certify products, replace qualified review or guarantee approval.

Evidence: Compliance-dashboard announcement and seller feedback

03 · Merchandising × Publishing owner

Change one specification without losing sight of the whole family.

Inspect the affected scope before publishing and the actual result afterward—not just the upload receipt.

Explore the work, exceptions and acceptance
Where the work breaks
A local edit affects parent/child relationships or several markets. Without a before-state and storefront check, the wider effect is discovered late.
Evidence to bring
Product facts, parent/child links, target market, prior content, proposed field changes, submission batch and channel responses.
How the product helps
AI explains field changes and related items. Prepare a scoped proposal, submit through authorized APIs or RPA after approval, then inspect receipts and page state.
Who makes the important decision
Operations approves scope, product facts and batch. Restoring old content also requires review rather than overwriting a newer version.
Branches to rehearse
Unsupported specification: request evidence. Expanded scope: reapprove. Accepted upload but unchanged page: reconcile. Error: prepare a restoration proposal.
What the team receives
The change set, affected items, approved version, responses and storefront checks.
What to measure
Affected-item count, time to detect differences, rework and mismatched responses.
Delivery dependencies and boundaries
Validate channel fields and relationship rules independently. Do not promise one-click rollback where the platform does not support it.

Evidence: Seller report: a variation edit affected related listings

04 · Purchasing × Inventory × Finance

When inventory is lost, do not start the evidence trail from scratch.

Purchase cost, landed cost and claim-eligible cost are not interchangeable.

Explore the work, exceptions and acceptance
Where the work breaks
SKU, batch, purchase evidence and loss events are disconnected. Teams search invoices and reconcile units only after a loss.
Evidence to bring
Inventory events, SKU/batch identifiers, purchase originals, unit prices and quantities, currencies, existing reimbursements and applicable rule versions.
How the product helps
The evidence application extracts source-linked records, separates cost components under the relevant rules and prepares a finance-review package.
Who makes the important decision
Finance verifies costs and evidence. Authorized owners decide whether to dispute and submit.
Branches to rehearse
Complete evidence: review. Unit mismatch: reconcile. Missing invoice: request it. Previously handled: link the original case, not a duplicate claim.
What the team receives
Batch-level cost evidence, missing items, review findings and a draft submission package.
What to measure
Preparation effort, evidence coverage, missing-document rate and age of unexplained reimbursement differences.
Delivery dependencies and boundaries
Validate SKU/purchase/batch mapping first. No fabricated invoices, substituted cost definitions or guaranteed recovery.

Evidence: Platform reimbursement cost definition · Seller report: preparing cost evidence

05 · Finance × Warehouse × Operations

The reimbursement was reversed. Did the stock return?

Money and inventory events may occur on different dates—and the case may still be open.

Explore the work, exceptions and acceptance
Where the work breaks
Finance sees a debit, the warehouse sees inventory and operations sees a closed case. No one can explain the combined outcome.
Evidence to bring
Reimbursement/reversal references, SKU and shipment, inventory ledger, quantities, event times, cases and decisions.
How the product helps
The settlement specialist links events by reference and goods chain, separating reimbursement, reversal, recovery and availability. Insufficient evidence stays unresolved.
Who makes the important decision
Finance classifies the difference, inventory owners verify stock records, and authorized people decide disputes and accounting treatment.
Branches to rehearse
Matched evidence: review for closure. Debit only: seek stock evidence. Cross-period event: link history. Unknown outcome: no automatic closure.
What the team receives
A money/stock timeline, unexplained differences, source references and owner tasks.
What to measure
Unexplained amount and age, resolution cycle and duplicate cases. A difference is not recovered revenue.
Delivery dependencies and boundaries
Events may span periods and have many-to-many relationships. Do not force matches by date or amount alone.

Evidence: Seller report: reimbursement reversal and inventory records

06 · Service × Fulfilment × Finance

Before the next refund or replacement, establish what happened.

Customer messages, tracking corrections, delivery evidence and payment disputes need one timeline.

Explore the work, exceptions and acceptance
Where the work breaks
Incorrect tracking and later delivery evidence are scattered across systems and email. Service and finance may initiate conflicting remedies.
Evidence to bring
Original/replacement orders, tracking events, original messages, delivery evidence, refund/dispute states and submission deadlines.
How the product helps
The exception specialist reconstructs facts and corrections, exposes evidence gaps and previous actions, and prepares a response package and owner tasks.
Who makes the important decision
Service decides communication and commercial concessions; finance verifies payment status. Authorized owners approve remedies, promises and submissions.
Branches to rehearse
Delivery evidence: prepare a dispute package. Missing evidence: collect it. Replacement plus refund request: cross-check. Unknown payment: query the original request, not a second refund.
What the team receives
A verifiable timeline, evidence list, resolution decision and post-action verification.
What to measure
Preparation time, missed deadlines, duplicate remedies and time in unknown state. No guaranteed dispute outcome.
Delivery dependencies and boundaries
Adapt to the actual platform and payment process. Minimize personal data and respect account and risk controls.

Evidence: Merchant report: corrected tracking and a payment dispute · Payment-dispute evidence guidance

FROM A FOCUSED APP TO INDUSTRY COORDINATION

Assemble around the outcome you own.

Availability and launch coordination

Combine supply analysis, evidence review and publication checks so launch plans reflect sellable stock, pending materials and actual storefront state.

Money-and-stock exception review

Connect purchase evidence, reimbursement reversals and order remedies. Finance, inventory and service retain their decisions without rebuilding separate versions of the facts.

Operating review and reusable expertise

Review confirmed causes and turn lessons into candidate rules or skills. Test before release; an individual rejection does not automatically rewrite business policy.

CHOOSE THE FIRST DELIVERY SCOPE

Validate an outcome before widening execution.

Start: evidence and review

Choose a stock or order exception set and produce a source-linked review list. Identifiers, timestamps and missing records are the main dependencies.

Extend: cross-role follow-up

Add a second source, owners, waiting, escalation and handoffs. Establish who owns each state; a delivered notification does not close the work.

Deepen: controlled execution

Validate permission, duplicate handling and result checks for each API or RPA action. Routine actions operate within authority; cost, price, publishing and external commitments remain owner decisions.

EXPERIENCE THE HANDOFF

Change the conditions. Explore the human handoff.

These general rehearsals demonstrate inventory, listing and order-exception branches. Your channel rules, evidence and approval conditions are confirmed in your project’s Scenario studio.

MORE THAN ANOTHER CHAT WINDOW

Ground the interpretation, decision and action.

AI applications: interpret the change

Interpret documents and context, expose sources, gaps and conflicts, and prepare reviewable outputs. Do not invent missing business facts.

Explore AI applications

Data and low-code: align facts and ownership

Align identifiers, timestamps and metric definitions with the data layer. Use configured forms and existing approvals for missing data, reviews and exception handoffs.

Explore the platform

QBotRPA and workers: follow through

Use authorized APIs where available, or validated RPA paths for interface-only systems. Digital roles follow receipts and pending tasks; reconcile unknown outcomes before retrying.

Explore QBotRPA

FROM THE BUSINESS ISSUE TO A DELIVERY PLAN

Rehearse the difficult handoff before committing to delivery.

Bring a matched set of records

Choose a recent exception. Bring the source documents, revisions, system states and human handling record together, with sensitive information redacted.

Test different outcomes

Vary data completeness, external confirmation and the owner’s approval or rejection. Agree when to proceed, wait, change the plan or stop.

Retain a deliverable scope

Freeze field definitions, responsibilities, API and RPA dependencies, human decisions and acceptance cases. Keep unresolved conditions visible.

Compare comparable samples for hands-on time, whole-record correctness, exception resolution and actual running cost. Include failures, waiting and rework; model extraction scores and generation counts are not business outcomes.

CHECKABLE OPERATING EVIDENCE

Evidence for the scenario. Your samples for the result.

View public evidence and its limits

Official guidance establishes operating constraints. Practitioner reports establish reported events, not industry prevalence. These sources imply no endorsement or partnership. Validate applicability by marketplace, route, contract and effective version.

Seller report: closed shipment, unavailable stock
A seller report and platform response distinguish shipment status from availability. Not a receiving-time benchmark.
Compliance-dashboard announcement and seller feedback
A seller reports unavailable listings and inventory exposure while materials await review. Historical experience is not a current review-time promise.
Seller report: a variation edit affected related listings
Used for the reported editing event, not as authoritative policy on review sharing.
Platform reimbursement cost definition
For applicable pre-order inventory losses, sourcing cost differs from sale price and landed cost. Check the claim category and current version.
Seller report: preparing cost evidence
A public request dated 6 October 2025 describes difficulty organizing cost records. Individual evidence only; promotional replies are excluded.
Seller report: reimbursement reversal and inventory records
A seller reports difficulty matching reversals to recovered stock. The platform response notes that event dates can differ.
Merchant report: corrected tracking and a payment dispute
The merchant’s 30 May 2025 post describes conflicting notices, tracking and later delivery evidence. Later software-vendor replies are excluded.
Payment-dispute evidence guidance
Some evidence is collected automatically; merchants still supply additional facts. The dispute process determines the outcome, with no guaranteed win.

Research checked on 24 October 2026. Validate priorities with the business owner using recent redacted samples.