How Hasil works

A wholesale portal for buyers.
One engine across your operations.

Hasil joins the part your buyers use with the systems your team already runs. It is a private ordering experience and the operational path behind every order—not another isolated connector.

Try the live portalSee pricing

The problem

Two tools can create two versions of the truth

Wholesale operations often begin with two separate purchases. One app gives buyers special prices inside or beside the storefront. Another integration moves records between the storefront and the ERP. Each has its own subscription, configuration, support queue and idea of what happened to an order.

That division becomes operational work. A buyer sees one total, the store records another, and the ERP receives a third document later. Teams compare screens, repair SKUs and ask which system should be believed. The problem is not simply moving more data. It is preserving one commercial truth from the buyer’s first view through fulfilment.

What Hasil is

The portal and the engine are one system

Hasil Pricing is the buyer-facing side. It gives each invited trade customer a private portal on your subdomain, a catalogue scoped to them, and the prices and quantity breaks you negotiated. It does not modify your storefront theme or expose wholesale terms to retail shoppers.

Hasil Sync is the operational side. It carries orders toward your ERP and carries catalogue, stock and prices back toward the storefront. Together, the portal and engine preserve one order from intent to draft documents. You can subscribe to either product separately, but they follow the same platform-neutral model rather than behaving like unrelated apps.

Wholesale order flow

One agreed total, carried through six steps.

01

Invite the buyer

You invite a trade customer to a private portal on your own Hasil subdomain. Retail shoppers never see it, and each buyer signs in to the catalogue you chose for them.

02

Assign the negotiated price list

The buyer sees their agreed prices, quantity breaks and permitted products rather than the public retail catalogue. Different buyers or groups can receive different terms without changing the storefront theme.

03

The buyer places a portal order

They build an order, review the agreed total and submit it inside the portal. Hasil records the order reference needed to move it safely through the rest of the flow.

04

The agreed total lands in the storefront

Hasil creates a draft order in the storefront you already operate. Where a platform accepts line prices, they are written directly; where it recalculates them, Hasil preserves the agreed order total with the platform’s supported adjustment method.

05

A draft sales order reaches the ERP

The same commercial order reaches your connected ERP as a draft quotation, estimate or sales order, according to that system’s real document model. Your team remains responsible for checking and confirming it.

06

You invoice and ship from your store

Payment, invoicing, tax, fulfilment and customer service stay in the systems you already control. Hasil never becomes the seller of record and never touches buyer funds.

The return path

Catalogue, stock and prices flow the other way

Orders begin with buyers and move inward. Operational data normally begins in the ERP and moves outward. Products, SKU mappings, available quantities and price-list facts can refresh automatically every six hours or whenever your team starts an on-demand run. The ERP remains the master for the fields it owns.

Timing follows what each platform genuinely supports. Where a storefront or ERP sends a useful event, Hasil responds to its webhook rather than waiting. Elsewhere, scheduled reads provide the safe fallback; supported storefront-order polling runs every ten minutes. Hasil does not claim instant delivery where a platform does not offer it, and the engine uses declared capabilities rather than hidden platform exceptions.

Any storefront × any ERP

The matrix is the product rule.

Every registered storefront can pair with every registered ERP. “Early access” means the platform is available by invitation; “Soon” means it is not yet available. These labels come from the same status inventory used across the site.

Hasil storefront and ERP compatibility matrix
StorefrontOdooLiveZoho InventoryLiveQuickBooks OnlineLiveXeroLiveERPNextSoonNetSuiteSoonDynamics 365SoonSAP Business OneSoon
ShopifyLiveLiveLiveLiveLiveSoonSoonSoonSoon
WooCommerceLiveLiveLiveLiveLiveSoonSoonSoonSoon
BigCommerceLiveLiveLiveLiveLiveSoonSoonSoonSoon
SallaEarly accessEarly accessEarly accessEarly accessEarly accessSoonSoonSoonSoon
MagentoEarly accessEarly accessEarly accessEarly accessEarly accessSoonSoonSoonSoon

Storefronts

ERP and accounting systems

Read the current deep-dives for BigCommerce, WooCommerce, Magento, Odoo, Zoho Inventory, QuickBooks Online and Xero.

What Hasil is not

It does not replace the systems you trust

  • Hasil is not accounting software. It does not post journals, close periods, reconcile bank accounts or calculate your tax obligations.
  • Hasil does not replace your storefront. Your store remains the place where orders are invoiced, fulfilled and managed.
  • Hasil does not replace your ERP. The ERP remains the operational system of record for the catalogue, stock and commercial documents you choose to sync.
  • Hasil is not a second place for manual entry. The point of the engine is to carry the same order and product facts between the systems that already own them.

Security and data

Small data footprint, explicit boundaries

Merchant records are protected with row-level access rules, so an authenticated merchant can reach only their own operational data. Sensitive connection credentials stay in the encrypted backend rather than browser storage. Raw webhook and sync payloads are retained for no more than 30 days and then purged automatically.

Product errors use first-party telemetry with sensitive values scrubbed before storage. Marketing analytics is separate and loads only after consent; it is suppressed inside buyer portals and the public demo. Read the complete handling and retention terms in the Privacy Policy.

Pricing

Choose the part you need

Hasil Pricing and Hasil Sync have separate plans, each with a 14-day trial. Subscribe to the portal, the engine or both; the bundle discounts the second product rather than forcing two full subscriptions. See the current plan limits and prices on the pricing page.

FAQ

How Hasil works, answered plainly

Is Hasil just an e-commerce connector?

No. A connector moves records between two systems. Hasil also gives your wholesale buyers a private place to sign in, see negotiated prices and place orders. The portal creates the commercial order; the engine then carries that order through your storefront and into your ERP.

Do buyers pay Hasil?

No. Hasil never holds or processes buyer funds. The portal sends an order at the agreed total to your storefront as a draft. You invoice, collect payment and ship through the processes you already use.

Which system is the source of truth?

Each data type has one owner. Your storefront owns incoming commerce orders. Your ERP normally owns catalogue, stock and price-list data when Hasil Sync is enabled. That one-master rule prevents conflicting edits and sync loops.

How quickly does information move?

Events move in seconds when a platform sends a suitable webhook. Where it does not, Hasil reads on a schedule: catalogue, stock and prices refresh every six hours or on demand, while supported order polling runs every ten minutes.

Can I use the portal without ERP sync?

Yes. Hasil Pricing and Hasil Sync are separate products. You can start with the buyer portal alone, add the sync engine later, or subscribe to both when you need the complete flow.

Walk through the buyer side.

Open the live demo without creating an account, then explore the two products separately if you need more detail.

Try the live portalHasil PricingHasil Sync