API integration · Haravan → MISA AMIS

Haravan → MISA AMIS V2 — one shop, multiple AMIS accounts

Businesses running one Haravan shop but accounting on multiple MISA AMIS companies (groups, legal entities, databases) — without installing multiple apps. GenNova Dev Haravan → AMIS V2 connects multiple AMIS accounts on one mapping: each company / database has its own token; set a default account and assign accounts per branch, sales channel, order source or carrier via sub-mapping.

Businesses running one Haravan shop but accounting on multiple MISA AMIS companies (groups, legal entities, databases) — without installing multiple apps. GenNova Dev Haravan → AMIS V2 connects multiple AMIS accounts on one mapping: each company / database has its own token; set a default account and assign accounts per branch, sales channel, order source or carrier via sub-mapping.

Orders, products, customers and inventory documents sync to the correct AMIS tenant automatically 24/7 via webhooks and schedules. Each document has its own log with an AMIS account prefix for reconciliation. Shares the haravan_to_amis license — no extra package for V2.

  • Multiple AMIS accounts
  • Branch / channel mapping
  • Orders & inventory
  • Per-AMIS logs

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 Add multiple AMIS V2 accounts (company / database), set default account
  3. 3 Configure sub-mapping: assign AMIS per branch, channel, source, carrier
  4. 4 Fetch source data via real-time webhooks, scheduled sync or manual runs
  5. 5 Filter orders and pick target AMIS account per mapping layer
  6. 6 Convert orders → AMIS sales docs; products → items; customers → objects
  7. 7 Call AMIS Save API on the correct tenant; callback updates status
  8. 8 Write detailed sync logs for lookup and error handling

Synced data

Sales orders

Convert Haravan orders to AMIS sales documents (PBH) and purchase orders (ĐĐH).

  • sync_orders
  • report_orders

Products & variants

Sync AMIS items from Haravan catalog; supports combos and local cache.

  • sync_products_to_db
  • sync_products

Customers

Create / update AMIS objects from Haravan customers.

  • sync_customers

Inventory documents

Purchase, return, transfer and adjustment docs from Haravan Admin to AMIS.

  • sync_inventory_purchase_orders
  • sync_inventory_purchase_returns
  • sync_inventory_transfers
  • sync_inventory_adjustments

Mapping configuration layers

  • Haravan branch ↔ AMIS branch
  • Haravan warehouse ↔ AMIS warehouse
  • Sales channel / payment gateway
  • Product type, account item, project
  • Payment method, customer object
  • Multiple AMIS V2 accounts (company / database)
  • Default account & assignment per branch / channel

Business benefits

  • One Haravan shop → multiple AMIS companies / databases — no extra apps
  • Assign AMIS accounts per branch, channel, order source, carrier
  • Same entities as V1: orders, products, inventory, customers
  • Detailed per-document logs — lookup by AMIS account
  • Webhooks + scheduled sync 24/7 — operations and accounting on one source
  • Shares Haravan → AMIS license — deploy V2 without buying another plan

FAQ

What does Haravan → MISA AMIS sync?

Sales orders, products, customers, inventory documents (purchase, return, transfer, adjustment) and cash receipts — with Haravan branch mapped to AMIS branches and warehouses.

Do I need manual entry on AMIS?

No. When webhooks or scheduled sync runs, data is transferred automatically per your mapping.

Is there a log per document?

Yes. Each sync writes detailed request/response logs for lookup and troubleshooting on the dashboard.

Real-time or scheduled?

Both: Haravan webhooks on new orders and bulk sync by date range on the dashboard.

How long to deploy?

Typically 1–2 weeks: connect APIs, map branches/warehouses, test a few orders and enable automation.

Haravan vs MISA naming — will it match?

Yes. This page is optimized for Haravan to MISA / MISA AMIS sync keywords.

Can one Haravan shop connect to multiple AMIS accounts?

Yes. AMIS V2 lets you add multiple companies / AMIS databases on one mapping. Set a default account and assign accounts per branch, channel, order source or carrier via sub-mapping.

Do I need a separate license for AMIS V2?

No. V2 shares the haravan_to_amis license. V1 and V2 data live in separate tables and do not overwrite each other.

Start free Contact us About GenNova Dev