Connect the store you have to JIWA

JIWA’s REST API runs as a plugin on your environment, not as a public multi-tenant URL. The store already takes orders. We will tell you whether those orders should become SalesOrders against Debtors, and what it takes to reach the box that hosts the API.

Book a free 30-minute discovery callTalk through your JIWA connection

Australian team. We look at the store and the JIWA environment before anyone talks about a connector.

Still running a store that needs JIWA?

The store still takes orders. JIWA still holds the debtor, the price tier and the stock the warehouse will pick. That is why the connection has been left as a CSV, a Solution Provider export, or someone keying sales orders after checkout.

JIWA is Australian-owned ERP and business-management software — Jiwa Financials, since 1995 — for wholesalers, distributors and manufacturers: accounting, inventory, sales and purchase orders, pricing. The vendor says it is designed for AU and NZ regulatory needs, developed locally, and sold via Jiwa Solution Providers throughout Australia and New Zealand. The homepage says it connects to “POS, EDI, webstores and more”. That is JIWA’s product claim, not a CoSource case, and not an install-base number. Third-party buyer-guide figures are not treated as official here.

This is the same wholesale and distribution segment as many B2B nopCommerce stores. The API is still on your JIWA box.

You might recognise one of these:

  • Web orders sit in the store until someone keys a Sales Order in JIWA
  • Debtor accounts and price tiers live in JIWA; the site shows a list price
  • The REST API plugin is not installed, or nobody knows which host it runs on
  • A Solution Provider set up a file drop, and it has been failing quietly
  • You are on JIWA 7, or on 8, and the API docs you found assume the other
  • You expected a Xero-style public URL and found a Windows service instead

You do not need a new storefront. You need a clear read on the JIWA environment you already have.

Why these connections stall

JIWA documents a REST API — HTTP verbs, default JSON DTOs (ServiceStack) — provided as a Jiwa plugin. It is hosted as a Windows service (self-hosted) or as a web package. Auth is an /auth session cookie, or an API Key (Bearer or query) from JIWA 7.2+. Docs describe Debtor (customer) and SalesOrders routes. JIWA 8 REST requires SQL Server 2016+ and JIWA 8.00.00+. The stall is rarely “JIWA has no API”. It is reaching the plugin, and pricing.

Plugin on your box

Not public SaaS

Debtors and tiers

No published case

There is no public multi-tenant URL.

This is not Xero. The API surface is plugin-hosted on the customer’s JIWA environment. If the Windows service is down, if the web package is only on the internal LAN, or if the Solution Provider never installed the plugin, the store in the cloud has nothing to call. Hosting and network are the first half of the job. We will not pretend a SaaS base URL exists.

Version and SQL edition are gates.

JIWA 8 REST wants SQL Server 2016 or later and JIWA 8.00.00 or later. An older 7.x file may have API keys from 7.2+ and a different host story. “We have JIWA” is not a version. The first call has to name the build and whether the plugin is actually running.

Debtors and price tiers are the B2B job.

Typical ecommerce work is Debtor list, read and create; SalesOrders from the webstore; stock and multi-price-tier reads. Pricing complexity is a vendor talking point for a reason. If the site sells the list price and JIWA would have sold tier 3, the integration has already failed the sales team. The store has to read the price JIWA would have used for that Debtor, not invent one.

We have not published a JIWA ecommerce case.

NESS is nopCommerce with Dynamics NAV 2018. Windsor is Peach and Xero. Neither is JIWA. We will not invent a “widely installed in Australian wholesale” count. There is no CoSource marketplace listing.

None of that makes the debtor file or the price matrix worthless. It does mean “call the JIWA API on Monday” is usually the wrong first move if nobody can reach the plugin.

How we work

We start with the JIWA host and the plugin, not with a public API key.

1

Look at what you have

JIWA version (7.x or 8.x), whether the REST plugin is installed, self-hosted service or web package, how a cloud store would reach it, Debtor and price-tier setup, and the store (nopCommerce, AbleCommerce, Shopify, or another CMS). We will tell you whether the API is callable before we talk mappings.

2

Decide the job

There are three honest outcomes. We recommend one, not all three.

3

Do the work in stages

Reachability first. Then Debtor reads and the price the site is allowed to show. SalesOrders up. Stock when the warehouse number must appear on the site. A file drop does not get a second life because it still runs on Fridays.

4

Hand it back so the next person can run it

Source, the plugin host and auth, a short record of what posts which way, and a connection someone else can understand.

Three honest outcomes

  • Connect the store to JIWA via the REST plugin when it is installed and reachable: Debtor list/read/create, price-tier reads, SalesOrders from the webstore, stock when the site must show a number
  • Fix a broken connector when a custom job or Solution Provider file drop still almost works: get it onto the REST plugin, stop posting at list price, or move the service off a machine the store cannot see
  • Decide not to connect when the plugin cannot be hosted safely, when the Solution Provider already owns a working webstore module, or when the site should stay brochure and orders should stay in JIWA

We will not tell you JIWA is a public cloud API. We will not invent an install-base. If you already know you want a Jiwa Solution Provider’s own webstore module and nothing custom, that provider is a better fit. If you want an honest design for the environment and the store you already have, talk to us.

What we need for the first call

A store URL and which JIWA environment is enough to start.

  • Which store: nopCommerce, AbleCommerce, Shopify, or another CMS — and a URL
  • JIWA 7 or 8, and whether the REST API plugin is installed
  • Self-hosted Windows service or web package — and whether a cloud host can reach it
  • How Debtors and price tiers work for web customers
  • Whether a web order should become a SalesOrder, and who owns stock on the site
  • What already posts: a Solution Provider file, EDI, or nothing
  • What “done” looks like: live SalesOrders, make the plugin reachable, or get a clear picture first

The first call is 30 minutes. You leave with a recommendation you can take to a manager, not a connector estimate pulled from thin air.

Related work

We have not published a named CoSource ecommerce case for JIWA. NESS is nopCommerce with Dynamics NAV 2018 — related B2B store-to-ERP work, a different product. Windsor is Peach and Xero. A JIWA environment still starts with its own assessment. We will not pretend it is a project we have already published.

FAQ

Is there a public JIWA API like Xero?
No. The REST API is a plugin on your JIWA environment — Windows service or web package. The store has to reach that host.
Which JIWA version do we need?
API keys from 7.2+. JIWA 8 REST requires SQL Server 2016+ and JIWA 8.00.00+. Bring the build.
Can the site use list price?
Often no, if JIWA would have used a Debtor tier. The integration has to read the price JIWA would sell at.
Do you have a JIWA case study?
No named published ecommerce case.
What if we only have the live store and a JIWA login?
That is common. Bring that, and whether anyone knows if the REST plugin is installed.

Talk through the JIWA connection you already need

Thirty minutes. Bring a store URL and which JIWA environment. We will tell you whether the plugin is reachable, whether to build Debtors and SalesOrders, or leave the current file drop alone for now.

Book a free 30-minute discovery call