ReUp Commerce Plugin

Why it matters

Some merchants want ReUp as the store, not a gateway bolted onto Woo. This plugin is that store-in-WP — historically synced to a ReUp API.

What it does

Merchant configures API credentials and P2P handles, manages catalog in a custom dark admin, and checks out customers through ReUp templates/shortcodes.

Operational advantage

Custom admin + P2P settings + REST mapping is a large plugin. The 1.6.x line includes substantial alignment docs.

Build vs buy

Skip the dark admin, gateway table, and backend-mapped REST — or skip this listing and take Local First if you want no remote API.

Interface advantage

Non-default Woo chrome: sidebar for dashboard, wallet, products, inventory, settings — it looks like a product.

What makes this different

Woo-optional, P2P-first, custom admin — different architecture from Local First and from Woo gateways.

Where this gets used

• P2P store on WordPress without Woo as the catalog
• Agency-branded ReUp install

Commercial paths

• Tiered WP plugin (Free/Pro-style gates appear in UI)
• Sold with ReUp API access
• Migration path toward Local First for buyers who want out of the API

Best buyer fit

Buyers who want the v1 ReUp-in-WordPress experience and will run or retire `api.reupbot.com`-class backends.

Current status

Available (v1.6.2 line in packaging). Stripe/PayPal tiles may show inactive. Version constants have drifted in copies — confirm the zip.

Notes

v1 is backend-dependent. Local First is the self-contained rewrite. Do not advertise both as the same architecture.