BigSeller API Integration Onboarding Guide

Looking to connect your accounting system or brand website, or let AI analyze your BigSeller business data? This guide walks you through applicable scenarios, onboarding steps, what to prepare, and how to get in touch.

Your business data in BigSeller — orders, inventory, billing, wallet balances, and more — can be connected on demand via the OPEN API to:

• Accounting systems — business alignment

• Own brand websites — order coordination

• AI agents — business analytics

Interfaces and fields are confirmed based on your needs; the actual data connection is implemented by an integration program.

01 What Can the API Do for You

The API moves your existing business data into the systems and workflows you need. Its core value includes:

• Connect systems and reduce repetitive rework — retrieve business data programmatically, then transform and map it according to your target system's requirements.

• Coordinate operations across orders and inventory — design closed-loop workflows around needs such as order ingestion and inventory queries.

• Power analysis with your own reports — combine the API with BI tools or AI agents to produce business analytics tailored to your team.

What is the BigSeller API, and who is it for?

An API is an interface that allows external programs to access business capabilities and data under agreed terms. It suits customers who want to connect BigSeller with accounting software, their own brand websites, in-house systems, data dashboards, or AI agents.

If you only check your data occasionally, start by reviewing the existing features and export options. Consider API integration when you need continuous syncing, cross-system processing, or scheduled analysis.

02 Scenarios and Use Cases

The following are illustrative examples intended to help you describe your requirements. They do not represent delivered customer cases or ready-made built-in features.

Case 1 (Website Coordination): Brand's Own Website — Order Processing and Available Inventory

Common need

• Orders are placed on the brand's website and should be processed centrally in BigSeller, while the website receives available inventory levels from the agreed warehouses.

Data flow

• Website order → integration program → BigSeller order processing

• Website or intermediary service → actively queries BigSeller inventory → updates available quantities on the website

Example

• After a customer places an order on the website, the integration program validates the product and order details before passing it into BigSeller. The website queries inventory at an agreed frequency and adjusts displayed quantities based on safety stock rules.

Confirm before connecting

• Permissions for the order-creation interface

• SKU and warehouse mapping

• Duplicate order identification

• Cancellation and refund workflows

• Rules that trigger inventory locking and release

Acceptance criteria

• Repeated submissions of the same order must not create duplicate orders; invalid SKUs must be traceable; inventory anomalies must trigger alerts. Inventory locking, shipment, and status callbacks follow the actual interfaces and business rules; scheduled syncing may still involve delays, and zero overselling cannot be guaranteed.

Case 2 (Accounting Coordination): Kingdee Integration — Turning Business Data into Finance-Ready Data

Common need

• Operational data lives in BigSeller while bookkeeping and financial analysis happen in Kingdee; the goal is to reduce manual exports, data cleansing, and duplicate entry.

Data flow

• Kingdee or an intermediary service pulls data from BigSeller → cleansing and field mapping → generates or imports vouchers per Kingdee's rules → finance reconciliation

Example

• Each day, retrieve the agreed scope of order, billing, and wallet data; organize it by shop, currency, and business date; and produce a data checklist and variance report for reconciliation.

Confirm before connecting

• Kingdee version and its open capabilities

• Voucher types and account mapping

• Currency and exchange rate handling

• Refund and expense definitions

• Sales revenue, receipts, and profit must each be defined separately and must not be mixed

Acceptance criteria

• Source records are traceable, amounts and transaction counts reconcile, and repeated runs do not generate duplicate vouchers. If you need SKU-level accounts-receivable data, confirm with customer service first whether it is available and what scope it covers.

Case 3 (AI Agent Analytics): Business Analytics Assistant — From Questions to Traceable Daily Reports

You can currently connect AI tools and agents such as Codex, WorkBuddy, Claude, and Doubao to your BigSeller business data to help generate business analytics and reports. For tools that support MCP, we also recommend connecting via MCP so the agent can retrieve business data on demand; the specific connection method depends on the tool's API capabilities and runtime environment. To learn how to connect via MCP, see "MCP Integration".

Common need

• The person in charge wants a daily view of order changes, key shop performance, and inventory risks — without repeatedly assembling multiple spreadsheets.

Data flow

• Ask a business question → API retrieves data → program cleans and computes → AI explains the changes → human review or authorized sharing

Example

• Every day, summarize the previous day's orders, compare recent performance by shop and currency, and flag shops with significant order-volume changes. Combine available inventory with sales data to build a watch list of SKUs that need attention.

Confirm before connecting

• Available fields and the reporting time zone

• Order statuses, currencies, and refund handling

• Delivery channels for reports, and how the analytics platform may use the data

Acceptance criteria

• Numbers are computed by the program, and reports state the data time range and definitions. If a data pull fails, the report must clearly flag the gap — missing data must never be presented as zero sales. Automatic sharing to group chats requires additional configuration of messaging channels and permissions.

03 How to Apply and Get Started

From requirement confirmation to formal activation, integration involves five stages:

Stage	What happens
STEP 1  Confirm requirements	Interface types, number of fields, call frequency, and business goals
STEP 2  Submit account information	Provide your BigSeller account; the integration party generates the app key per the workflow
STEP 3  Deliver integration documentation	Obtain the API documentation for your account and hand it to the implementation team
STEP 4  Customer testing	Test against the documentation, run continuously, and verify data accuracy and stability
STEP 5  Confirm and pay	After confirming everything works as expected, pay as agreed and complete activation

04 Pricing and Integration Inquiries

To explore API integration, contact your BigSeller account manager or official customer service directly, and describe:

• The system you want to integrate with

• Your business scenario

• The data you need

Share the specifics of your integration needs with customer service, and interfaces will be tailored to your requirements. The final price, currency, taxes, package contents, and validity period are subject to the formal quotation.

You may check our supported API details by below feishu links:

English Version -- BigSeller API
Chinese Version -- BigSeller API

05 FAQ

Q01. What should I prepare for my first inquiry?

• Business goal: the problem to solve and the outcome you expect

• Target system: system name, version, implementation party, and whether it offers an API

• Data scope: shops, warehouses, order statuses, historical time range, and required fields

• Data direction: read-only, or do you also need to push orders or perform other write operations

• Sync volume: daily data volume, execution frequency, acceptable latency, and peak requirements

• Project arrangements: technical contact, expected launch date, and trial acceptance criteria

You can share this information directly with your BigSeller account manager or official customer service to help evaluate the integration plan.

Q02. Do I need to provide my BigSeller login password when applying?

When applying for integration, you need to provide the BigSeller account information used to identify the account to be activated. Do not include your login password, verification codes, or app key in routine inquiry materials. How account identification information and keys are delivered will be explained by the official integration contact.

Once you receive the key, store it in a controlled server-side configuration or a secrets management tool — never in client-accessible web code, public repositories, or group-chat screenshots.

Q03. How long does it take from application to going live?

The timeline depends on the interface scope, the target system's conditions, field-mapping complexity, and testing results; the exact duration will be confirmed after requirements are assessed. Read-only reporting projects and projects involving order writes or accounting mappings typically differ in implementation effort.

After requirements are confirmed, we recommend agreeing on four milestones together: documentation delivery, first joint test, trial run, and acceptance.

Q04. During the trial, how do I know the integration "works"?

A single successful request is not enough. We recommend verifying that:

• All required fields are present

• Paginated data is complete

• Samples match BigSeller

• Repeated executions do not create duplicate records

• The process recovers after errors

• The system stays stable at the agreed call frequency

If the integration involves order ingestion or accounting vouchers, also verify business statuses, amount definitions, idempotency and deduplication, and callbacks/receipts. Trial duration, quotas, and test scope should be confirmed in advance.

Disclaimer

The use cases and technical suggestions above are intended to help you evaluate an integration plan. Actual interface capabilities, granted permissions, delivery scope, and costs are subject to the formal API documentation, service agreement, and quotation.