CRM, inventory, order and stock management
North America · Business System Development
North America Business System Development | Multi-store, multi-entity, multi-currency books that reconcile
Chinese-owned businesses in North America frequently operate entities on both sides of the Pacific, settle in USD and RMB, and face differing state sales tax rules. The system has to calculate multi-entity accounting, exchange rates, sales tax, platform commissions and refund splits correctly, otherwise finance adjusts entries by hand every month. We usually implement orders and funds first, then extend to inventory and staffing.
In short: Delivering Business System Development in North America begins by confirming the business boundary within ERP, CRM, inventory, approval workflows and operational platforms, then mapping data and process against the local compliance checklist (CCPA / CPRA and state privacy laws, ADA and WCAG 2.1 AA) before development starts. Deliverables cover Current-state and target process maps, Data model and permission matrix, System source code, database scripts and migration plan, so the system can be handed over to an internal team or a third party.
Scope of Business System Development
The activities below are the ones we own on this type of project, delivered in phases and confirmed item by item. Where third-party hardware or licences are involved, the procurement list, licensing requirements and responsibility split are set out at solution stage.
Approval workflows, contracts and financial reconciliation
Multi-store, multi-warehouse, multi-currency and multi-entity accounting
Integration with ERP, payment, logistics and tax systems
Reporting dashboards and operational analytics
Deliverables
Every item is archivable and transferable, so an internal team or a third party can maintain the system later.
- Current-state and target process maps
- Data model and permission matrix
- System source code, database scripts and migration plan
- API documentation and third-party integration records
- Training materials and acceptance report
Typical technology stack
Selected against the existing environment and the capabilities of your team, with maintainability and future extension in mind.
Java / Spring Boot
PHP / ThinkPHP
Node.js
MySQL / PostgreSQL
Redis
RabbitMQ / Kafka
BI dashboards
Implementation phases
Each phase produces a confirmable output and an acceptance record, so issues are resolved within the phase.
Phase 01
Process review
Map existing spreadsheets, legacy systems and manual steps; identify where duplicate entry and reconciliation cost the most
Phase 02
Scope and model
Confirm first-phase modules, role permissions and data migration boundary
Phase 03
Build and parallel run
Bring core modules live first, then validate data through a parallel run
Phase 04
Cutover and support
Retire the old system, archive data and provide a supervised stabilisation period
Compliance considerations in North America
For Business System Development, the requirements below directly affect data structures, page behaviour and deployment. We confirm each item during solution design; formal legal advice should be confirmed with a local adviser.
CCPA / CPRA and state privacy laws
California residents may request access, deletion and correction of personal information, and may opt out of sale or sharing. Sites need a clear privacy policy, cookie categorisation and a “do not sell my personal information” entry point; forms should collect only necessary fields and record consent time and source.
ADA and WCAG 2.1 AA
Website accessibility complaints under the Americans with Disabilities Act are not unusual in retail, food service and real estate. We implement WCAG 2.1 AA contrast, keyboard reachability, visible focus states, form labels and alternative text, and provide a self-assessment checklist you can use to answer client or legal enquiries.
FTC endorsement guides: endorsements and reviews must be genuine and verifiable
The Federal Trade Commission requires endorsements and reviews to be genuine and verifiable, with paid endorsement relationships disclosed. Cases on this site are compiled from delivery facts; client names are anonymised under confidentiality agreements, and content is stated in terms of implementation approach and project outcomes.
Sales tax nexus and payment compliance
Once cross-state sales exceed a state’s economic nexus threshold, registration and tax collection apply. Systems must support rate calculation by state and postcode plus exemption certificate management. Card handling follows PCI DSS requirements, and card numbers are never stored in our own databases.
Additional requirements in health, finance and education
Protected health information brings HIPAA into scope; lending and wealth products raise state licensing and disclosure considerations; services involving minors bring COPPA into scope. For these sectors we define the data boundary during solution design, then decide which function belongs in which system.
North America cases involving this service
The following projects involve Business System Development. Each shows how the challenge was scoped and what was delivered.
DTC furniture brand website rebuild, Los Angeles
Client: Furniture brand in Los Angeles (family-owned, name withheld under NDA)
Challenge
Acquisition depended on third-party marketplaces with rising commissions and advertising costs. The original template site could not carry the dimensions, materials and delivery terms of large furniture, so customers asked repeatedly before ordering and service cost stayed high. Product data was unstructured, which limited both search and advertising precision.
What we delivered
- Rebuilt the information architecture around room, category and material, adding dimensions, load rating, finish, care and delivery coverage fields
- Custom product and content console so the team can maintain multilingual copy and lifestyle imagery without a developer
- State-level sales tax calculation and zoned delivery rules, with a separate appointment flow for oversized items
- WCAG 2.1 AA remediation, including alternative text and full keyboard operation
Outcome
The site moved from a catalogue to a revenue channel: standardised product fields reduced repeat enquiries, advertising could split landing pages by category and scenario, and content updates no longer depended on an agency.
Delivery value: Standardised product fields and content structure leave the client with a reusable product-data asset: new categories, additional advertising channels and future redesigns extend the existing foundation rather than requiring a rebuild.
Multi-location ordering and loyalty system, New York
Client: Chinese restaurant group in New York (six locations, Chinese founding team)
Challenge
Each location used a different ordering tool and loyalty points did not transfer. Delivery platforms took a high commission while the in-house ordering experience was poor. Head office had no consolidated view of dish sales or margin, and purchasing relied on store managers’ judgement.
What we delivered
- Central menu and pricing service supporting per-location pricing, temporary sell-outs and packaging fees
- Own ordering app and mini-program covering dine-in QR ordering, pickup and local delivery
- Loyalty points and stored value usable across locations, with balances and transactions settled per store
- Head-office dashboard covering dish sales, margin, hourly traffic and store comparison
Outcome
Six locations now share one menu and one loyalty programme, and head office can see per-store margin daily. With a larger share of orders placed directly, dependence on platforms fell and promotions could be scheduled on the company’s own terms.
Delivery value: Menus, pricing, loyalty and settlement rules are consolidated into a group-level standard, so new stores onboard through one configuration process; daily per-store figures give a comparable basis for site selection, pricing and promotion.
Real estate CRM and listing sync, Bay Area
Client: Chinese real estate brokerage team in the San Francisco Bay Area (20+ agents)
Challenge
Listings arrived from multiple MLS feeds and developers in inconsistent formats. Client follow-up lived in individual agents’ WeChat and spreadsheets, so clients were lost when an agent left. The website listing pages lagged behind, and clients lost confidence on seeing sold properties still advertised.
What we delivered
- Listing aggregation and cleansing: unified fields, de-duplication, status and update timestamps
- CRM covering lead source, showing records, follow-up reminders and commission allocation
- Website listing pages synchronised on a schedule with MLS data, with withdrawn listings flagged automatically
- Agent mobile pages for on-site check-in, photo upload and immediate notes
Outcome
Listing status and the public website stay consistent, so clients no longer ask whether a property is still available. Client records moved from individual hands into a team asset, and staff turnover no longer takes the relationship with it.
Delivery value: Listing data and client records become team assets rather than personal resources, so staff changes hand over cleanly; listing status and the public site share one source, removing manual effort from keeping published information consistent.
Dental group appointment and records platform, Los Angeles
Client: Chinese dental practice in Los Angeles (three branches)
Challenge
Appointments ran on phone calls and a paper book at reception, with a high no-show rate. Patient records and imaging were split across three branches, so patients visiting another branch were registered again. Insurance claim information was incomplete, and reception called patients repeatedly.
What we delivered
- Online booking with automated SMS and email reminders, plus rescheduling and waitlist handling
- Patient master index sharing core records across branches, with imaging access controlled by role
- Insurance information and claim document checklists, with automatic prompts for missing items
- HIPAA-aligned access control, activity logging and encryption in transit
Outcome
Reception moved from booking by phone to handling exceptions. Cross-branch visits no longer duplicate registration, and missing claim documents are identified at booking rather than afterwards.
Delivery value: A cross-location patient master index and unified scheduling give the group a foundation for opening further clinics; complete visit and claim records support later compliance review and operational analysis.
West Coast fulfilment WMS and last-mile integration
Client: Chinese fulfilment provider in Los Angeles (four warehouses)
Challenge
Inbound receipts were logged in Excel and bin locations depended on experienced staff memory. Orders from several marketplaces were downloaded and re-entered by hand, causing mis-shipments. Multiple last-mile carriers meant tracking each shipment on a separate website.
What we delivered
- WMS covering receiving, put-away, picking, checking, packing and dispatch with barcode scanning throughout
- Automatic order synchronisation from major marketplaces, with a separate queue for exceptions
- Carrier API integration with consolidated tracking pushed to customers automatically
- Temperature-zone and key-area sensors feeding alerts to the on-duty phone
Outcome
Orders moved from manual re-entry to automatic flow and mis-shipments fell. Bin locations and stock are visible in real time, new staff no longer depend on experienced colleagues, and exception parcels have their own queue rather than being buried in chat history.
Delivery value: Barcode-driven, systemised workflows shorten training and detach operating standards from individual experience; with multi-platform orders and multi-carrier tracking connected, the warehouse can take on new channels and additional sites.
After-school education enrolment and academic platform, Toronto
Client: Chinese after-school tutoring and admissions preparation provider in Toronto
Challenge
Enquiry volume concentrated in the admissions season and was answered manually in WeChat groups, so leads were missed. Timetabling and teacher allocation ran on spreadsheets with frequent conflicts. Parents could not see progress, and renewal decisions lacked evidence.
What we delivered
- Brand site and course pages organised by grade, subject and target examination, with trial lesson booking
- Lead management with source tagging, follow-up status and automatic reminders
- Timetabling and teacher scheduling with conflict validation and cover arrangements
- Parent portal covering timetable, homework, periodic assessments and teacher comments
Outcome
Enquiries moved from scattered WeChat threads into a single pipeline with traceable follow-up. Scheduling conflicts are blocked in the system, and renewal conversations now rest on concrete progress records rather than sales narrative.
Delivery value: Leads, scheduling and teaching records become queryable operational data, so enrolment-season capacity no longer depends on staffing peaks; the parent portal gives renewal conversations an objective basis.
Accounting firm client portal and filing workflow, New York
Client: Chinese accounting firm in New York (SME and individual clients)
Challenge
Tax season documents arrived by email and WeChat with version confusion and repeated chasing for missing items. Sensitive financial data travelled through chat tools, creating confidentiality exposure. Internal progress was coordinated verbally and partners had no view of workload.
What we delivered
- Client portal generating a document checklist per tax season, with uploads archived and versioned automatically
- Missing-item reminders and deadline countdown to reduce manual chasing
- Internal work orders and progress board by client, filing type and owner
- Encrypted storage, download watermarking, access logs and role-based permissions
Outcome
Document collection moved from chasing clients to a checklist-driven process where gaps are visible immediately. Sensitive files no longer pass through chat tools, and partners can review workload by person and by client before assigning work.
Delivery value: Collection, version archiving and access control become auditable processes, and sensitive data no longer moves through messaging tools; seasonal workload can be measured per person and per client to inform staffing and capacity planning.
Multi-tenant SaaS backend for a startup team, Seattle
Client: Chinese founding team in Seattle (B2B tool product)
Challenge
Low-code had validated the product, but permissions, billing and data isolation could not support a growing customer base. Enterprise prospects required SSO, audit logs and data export. There was no dedicated operations engineer and releases were manual.
What we delivered
- Multi-tenant architecture rebuild covering tenant isolation, role permissions, quotas and rate limiting
- Subscription billing by seat and usage, trial conversion, invoices and statements
- Enterprise capabilities: SSO, audit logs, data export and deletion request handling
- CI/CD pipeline with monitoring and alerting, and a standardised release process
- AI-assisted features for document summarisation and ticket classification, with human review retained
Outcome
The product moved from demonstrable to contractable: security questionnaires can be answered with documentation, billing no longer relies on manual invoicing, and releases follow a defined process instead of taking half a day.
Delivery value: With tenant isolation, billing and enterprise capabilities in place, the product meets the qualification requirements of enterprise contracts; standardised release and monitoring processes let the team scale without a proportional rise in operations effort.
Case note: client names are anonymised under confidentiality agreements; cases are presented to explain implementation approach and delivery boundaries, and specific figures are subject to project acceptance records.
Business System Development FAQ
The first three answers are general; the last two address conditions specific to North America.
Can you extend an existing ERP?
Often, yes, but it is worth assessing first. Where the ERP exposes standard APIs we build peripheral systems and integrate; where only source modification is possible, we assess upgrade risk before committing.
Will data migration lose records?
We take a full backup and build a field mapping table, then run a trial migration and reconcile totals and sampled records. The legacy database stays read-only on cutover day until sign-off.
Will it cope with concurrent users?
Sizing follows expected concurrency. With sound indexing and caching, typical SME systems handle tens to hundreds of concurrent users; peak or bulk-entry scenarios are load tested as part of the plan.
How are timelines and meeting times arranged for Business System Development in North America?
Meetings and confirmation points follow the working hours common in North America (UTC−5 to UTC−8, 12–15 hours behind Chengdu). Requirements and solution design include a written progress update every week; development delivers a runnable build every two weeks. For cross-timezone work, key confirmations are placed inside the overlap of both working days, so progress never stalls waiting on a reply.
Which local compliance requirements should be confirmed in advance for Business System Development in North America?
Projects in North America typically involve CCPA / CPRA and state privacy laws, ADA and WCAG 2.1 AA, FTC endorsement guides: endorsements and reviews must be genuine and verifiable. These requirements directly shape data structures, page behaviour, hosting location and data retention, so each is confirmed at solution stage and recorded in the delivery documentation. Formal legal advice should be confirmed with a local adviser.
Other services in North America
Most projects combine two or three services, for example a website followed by a business system, or AI capabilities added after a system goes live.
Mobile App Development
An app for North American users has to pass review and retain users
Website Development
Brand and DTC sites: discoverability first, conversion second
AI Application Development
AI where it earns its place: triage, extraction, knowledge retrieval
IoT Development
Site data from warehouses, stores and cold chains, back to head office
System Operations & Maintenance
Taking over someone else’s system: assess before acting