Multi-shop Haravan sync — main & sub stores

Businesses running multiple Haravan shops (main and sub stores) need to sync orders, products and configuration across shops. GenNova Dev connects via Haravan webhooks and the web dashboard.

Doanh nghiệp vận hành nhiều shop Haravan.com (shop chính và shop phụ) cần đồng bộ đơn hàng, sản phẩm và cấu hình giữa các shop. GenNova Dev kết nối qua webhook Haravan.com và dashboard web.

Mapping linh hoạt, log mỗi lần đồng bộ — phù hợp chuỗi cửa hàng hoặc mô hình franchise.

  • Multi-shop
  • Orders
  • Products
  • Haravan webhooks

Sync process

Technical flow on GenNova Dev — from API connection to logging, based on the actual convert pipeline.

  1. 1 Connect APIs on both platforms and verify license / access rights
  2. 2 Configure branch, warehouse, sales channel and data mapping layers
  3. 3 Fetch source data via real-time webhooks, scheduled sync or manual runs
  4. 4 Filter orders / products by configured rules and mapping filters
  5. 5 Convert data to the target system format
  6. 6 Send data to AMIS, MeInvoice or Haravan / Nhanh.vn
  7. 7 Receive responses and update status, tags or notes on source records
  8. 8 Write detailed sync logs for lookup and error handling

Synced data

Orders

Mirror orders between main and sub shops.

  • sync_orders

Products

Sync catalog across shops.

  • sync_products

Inventory

Update inventory across shops.

  • sync_inventory

Mapping configuration layers

  • Main shop ↔ sub shop
  • Per-entity sync scope
  • Webhook endpoint

Business benefits

  • Sync orders, products, customers, inventory across Haravan shops
  • Flexible main ↔ sub direction (main_to_sub, sub_to_main)
  • Haravan webhooks — fulfillment, payment, refund updates
  • Scope cursor — control sync scope per shop

FAQ

Sync main and sub Haravan shops?

Yes. Configure shop mapping on GenNova Dev.

One-way or two-way?

Configure main→sub, sub→main or both as needed.