Questions & answers
Questions about the product mechanics, authority, Shopify, pricing, and the limits of the current preview.
A brand-funded, capped commercial right for one selected retailer location. Eligible purchasing builds Flex; the retailer can request to use part of it on qualifying slow inventory when it chooses enough fresh inventory under the brand’s active terms.
The hypothesis is not that Oplut invented stock rotation. It is that making a bounded right visible before the retailer’s next buying decision can change what the retailer buys, while the operating workflow keeps the promise controlled.
No. Flex is a conditional right. Store credit is one later possible outcome after approval, physical receipt, acceptance, discrepancy resolution, and separate authorization.
No. The brand chooses the retailer, period, earning rule, cap, eligible products, condition rules, fresh-purchase requirement, and approval authority.
Only when purchasing caused by Flex creates more contribution than the net cost of the program. The working equation is additional purchasing × contribution margin − net Flex cost after recovery = incremental supplier contribution.
No. They are an illustrative scenario, not customer evidence, a benchmark, a testimonial, an average, or a guarantee.
Then Flex created no incremental gross profit and the supplier is worse off by the net cost of Flex. Oplut is designed to keep that counterfactual visible.
No. A replacement order is a commerce fact. Causal purchasing change remains unverified unless the no-Flex alternative was stated and later evidence supports the difference.
The brand. It selects the retailer location, activates the terms, approves the exact request, records or reviews what was received, resolves differences, and separately authorizes final credit.
The retailer identifies the slow products it wants to move, chooses enough fresh inventory, returns the approved goods, and continues buying under the brand’s terms. The validation MVP does not require a separate retailer Oplut login.
No. Automatic approval, Return creation, Draft Order completion, or account-credit issuance is outside the current preview and requires separate future authority.
Missing, rejected, extra, or uncertain products remain visible and block unsupported credit until an authorized person resolves the difference.
No. The current product is a local synthetic Demo MVP. It does not install on a store, request Shopify scopes, read merchant data, or take an external action.
The synthetic experience is organized around Shopify B2B Company Location, order, return, Draft Order, and account-credit concepts. That makes the future integration testable without claiming the integration exists.
Company Location identity, orders, supported Return rails, account-credit state, payment, fulfillment, cancellation, and refund remain Shopify commerce facts in any later approved integration.
No. Do not submit Shopify credentials, retailer identities, order exports, private terms, or other merchant data through the public website.
A detailed synthetic product preview and a founder-led conversation about one retailer account. No live Shopify connection or real commercial action is offered through this website.
The working model is one monthly subscription with published bands based on active retailer locations. Exact launch rates are not yet published, and willingness to pay remains unverified.
That is not the current plan. Those values belong in the brand’s program economics, not in the proposed billing formula.
The thesis should be narrowed or stopped if qualified brands do not face repeated material cases, manual handling is adequate, economics are negative, retailer participation is too burdensome, or Flex does not materially change purchasing behavior.
Send it over without including merchant exports, credentials, or private account data.