WildApp Retail Pro Bridge · Wildcreative
production online Contact Open panel
Origin Retail Pro 9
catalog · price · stock
Sync state
2-way

Live · RP9 ↔ store bridge

web orders → sales orders
Destination Woo · Medusa · Shopify

Your POS and storefront,
on one command plane.

Multi-tenant SaaS bridge for Retail Pro 9 — catalog out, orders in, licensed agent, cloud panel. Built for integrators who ship real installs.

Open control panel → See install path

Why WildApp

RP9 still runs the floor. The webstore should not guess.

Retail Pro has no modern API. Shops still need live stock and clean order write-back. WildApp is the production pipe — multi-tenant, licensed, supportable — not another private script on a laptop.

Without a real bridge

  • — Stock lies online after a busy weekend
  • — Orders retyped into POS after midnight
  • — One developer’s folder holds the whole sync
  • — No clean revoke when a contract ends

With WildApp live

  • + Catalog, price & stock leave RP9 on a schedule
  • + Web orders land as sales orders in Retail Pro
  • + Panel for tenants, agents, mapping & logs
  • + Signed license, machine bind, cloud revoke

System map

What the command plane actually runs

Six load-bearing parts — same story as the orbit above, written for integrators.

SYNC.OUT

Catalog push

Items, prices, and inventory move from Retail Pro toward WooCommerce, Medusa, or Shopify.

SYNC.IN

Order intake

Web orders return as RP9 sales orders — documents the POS team already understands.

AGENT

Windows EXE

Sits next to Oracle. Enrolls with a token. Outbound HTTPS only — no hole in the shop LAN.

PANEL

Multi-tenant cloud

Clients, stores, mapping, agents, logs — one place for every subsidiary you support.

LICENSE

Ed25519 · machine-bound

Signed .lic, fingerprint, expiry, max agents, revoke from the cloud when a deal ends.

OPS

Visible operations

Heartbeats, job status, order flow — so support is not guessing which script died overnight.

Install path

Three stations to live traffic

From signed client to moving stock — without a multi-week science project.

Station 01

Issue the client

Create the tenant. Set duration & max agents. Download the signed license and enrollment token.

Station 02

Seat the agent

Drop EXE + license on the RP9 PC. Enroll. Connect Oracle. It only dials out.

Station 03

Map & release

Attach Woo, Medusa, or Shopify, set field mapping, run the first catalog cycle, watch orders land.

Fits your stack

Built for the systems you already sell

Connectors for real retail — not a demo that only works on one laptop.

Retail Pro 9 Oracle WooCommerce Medusa Shopify Windows agent Multi-tenant SaaS HTTPS · Let’s Encrypt

Trust layer

Security is part of the product

Retail credentials and store tokens are not “config in a chat.” They are the business.

  • Ed25519 signed licenses — caps and expiry are not editable on disk
  • Machine-bound agents — copying the folder does not create a free seat
  • DPAPI protects secrets on Windows · all cloud traffic is HTTPS
  • Revoke a license or a single machine from the panel when a deal ends
Network
Outbound-only agent

No inbound ports on the client network. The POS machine calls home.

Tenancy
Isolated per client

Agents, stores, and mapping stay inside each tenant boundary.

Cloud
api.wildapp.net

Production panel, rate limits, authenticated control plane.

Next action

Open the command plane

Already onboarded? Jump into the panel. Scoping a Retail Pro client? Talk to Wildcreative — installs, not vapor.

Open control panel → Email support
wildcreative.net wildapp.net · production