V0LTAdmin dashboard →API, feed, product URL or manual observation. Supplier SKU and credentials stay server-side.
SUPPLIER & INVENTORY ENGINEPrivate supplier data.
Private supplier data.
Simple customer answers.
The public website never needs the supplier URL. The engine checks private sources, caches the result and exposes only the price, availability and freshness needed for a customer decision.
ENGINEsetup requiredSafe fallback remains active
PRODUCTS8Public SKUs mapped
FRESH0Recent supplier observations
MERCHANT READY0Verified price + availability
One controlled pipeline.
Supplier failures do not automatically become customer promises. The engine falls back to stale data briefly, then hides the price/availability if the source is too old.
Convert supplier-specific price and stock into one V0LT data contract.
Write atomically. Fresh, stale and expired states prevent silent bad data.
Customers see Available, Low stock, Supplier order, Out of stock or Availability pending.
Current public snapshot
Last generated: Not yet. This table contains no supplier URL, private SKU, authentication header or landed-cost component.
PUBLIC SKUAVAILABILITYFRESHNESSPUBLIC PRICE
Loading snapshot…———
Hard boundaries
Only what helps the customer decide.
- V0LT public SKU
- Verified public price
- Customer-safe availability label
- Fresh / stale status
- Same-day capability when actually known
The supplier relationship stays private.
- Supplier URL
- Supplier credentials or API tokens
- Private supplier SKU
- Supplier purchase price
- Private landed-cost formula
Checkout hold rule: when a fresh supplier quantity is known, V0LT can create a 15-minute local checkout hold to stop V0LT from overselling its observed quantity. It does not pretend to lock the supplier's own stock; supplier availability is rechecked before payment/order submission. If the supplier exposes no quantity, confirmation is required instead of creating a fake hold.