Busy Accounting · Busy ecommerce
Busy ERP Ecommerce: Catalogue and Order Integration
An ordering portal needs two directions: catalogue, stock and customer price data for the buyer, then an order that the business can validate and record in Busy. Treat a submitted web order and a confirmed ERP sales order as separate states.
This guide describes a commerce integration to scope, not a live storefront. Confirm the enabled portal, branding/domain options, user access, supported Busy fields and order-write capability. Refresh timing, stock accuracy, launch dates and business outcomes are not guaranteed.
Illustrative workflow
Busy data to catalogue
Map permitted products, units, prices and stock locations with update context.
Buyer or representative selects
Use an authorized customer account and applicable ordering rules.
Submit for validation
Recheck stock, price, tax and credit rules; handle source connection failures.
Reconcile the ERP order
Confirm the recorded Busy reference, resolve rejected/duplicate orders and communicate the actual state.
Scope the commerce functions separately
Catalogue viewing, order entry and financial report access need different data and permissions. Availability must be confirmed for the actual setup.
Catalogue and stock
Map item masters, units, price lists, available quantities and selected godowns. Confirm barcode support separately.
Order conversion
Confirm whether submitted orders can become Busy sales orders and how errors and duplicate submissions are reconciled.
Customer account view
Scope ledger/outstanding visibility for the authenticated customer, using the report contract.
Connectivity
Agree unavailable-source handling. Do not assume offline ordering or background sync is supported.
Three readers, three permission scopes
An order placed on behalf of a customer should preserve the representative's identity, rather than hide who acted.
Sales representative
Confirm assigned customer access, customer-specific price rules and an auditable order-on-behalf workflow.
Customer
Confirm login method, permitted catalogue, account view and visible order states. A submitted order is not a dispatch promise.
Owner or operator
Review order exceptions, mappings, price/stock changes and reconciliation before fulfillment.
A periodic snapshot can go stale
Stock and prices can change between refreshes. Agree the interval, last-success indicator and failure state. Revalidate the order against available source rules before confirmation; a shorter interval alone cannot eliminate overselling.
On a narrow screen, scroll the table horizontally to read every column.
| Data direction | Fields to scope | Check before use |
|---|---|---|
| Busy → portal | Product masters and price rules | Supported units, variants, schemes and effective price |
| Busy → portal | Stock by selected location | Update time and concurrent sales |
| Portal → Busy | Customer, order lines and totals | Validation, duplicate handling and ERP reference |
| Busy → account view | Ledger and outstanding | Customer permission, period and reconciliation |
Check the rules that matter to your catalogue
For hypothetical auto-parts, garment, FMCG, pharmaceutical, chemical or distribution catalogues, ask which variants, locations, schemes, batches, expiry and pricing fields are supported. Do not infer regulatory compliance, automated license checks or correct tax treatment from an industry label.
Evaluate ordering with a bounded pilot
Track a defined order cohort: entry and review time, rejected/duplicate orders, stock exceptions and successfully reconciled ERP orders. Compare equivalent volumes and include setup, software and support costs. This page provides no productivity or collection improvement percentage.
Agree the branding and domain scope
White-label means a portal can be presented with agreed business branding, if supported. Confirm domain configuration, design options, operational ownership and separate-company permissions. Branding alone does not establish SEO gains, customer loyalty or lower infrastructure costs.
Busy remains the record to reconcile against
Define authentication, customer/company boundaries, authorized write operations and the handling of price, credit, tax and stock validation. Verify the configured order path rather than assuming every Busy rule is applied. Review logs, retention and signed availability/support terms separately.
Prepare the catalogue and order contract
Bring your Busy version, company and item mappings, customer scopes, unit/price/tax rules and a permitted example order. Agree domain and branding, connector deployment, refresh and order-validation rules, test cases, exception handling and launch responsibilities. No fixed implementation period is promised.
Questions about Busy ecommerce
Does a sync interval prevent overselling?
No interval guarantees that. Stock can change between updates or during an order. Confirm the source checks, reservation/validation behavior and exceptions before promising availability.
Can a representative order for a customer?
Confirm that order-on-behalf is enabled, which customers the representative may access and how their identity and permissions are recorded. Customer-specific pricing, schemes and credit rules need separate validation.
Are all Busy batches, schemes and offline features supported?
Do not assume that. Scope the actual fields, Busy version and connector behavior; confirm batch/expiry, variants, multi-unit pricing, scheme logic and offline operation individually.
Can we use our domain and view ledgers?
Confirm supported branding/domain setup and the customer report-access scope for your account. They are separate functions and do not prove financial-data isolation, uninterrupted service or a collection result.
Choose the next workflow
Review privacy terms and the Legal Center. Confirm support and availability in your signed service agreement.
Discuss your Busy ecommerce setup
An enquiry does not book an appointment or activate a product. Availability, setup, support and commercial terms need separate confirmation; binding commitments require a signed agreement.
Send an enquiry