Merchant responsibility
The storefront owner is responsible for products, claims, pricing, taxes, returns, warranties, customer obligations, and lawful operation.
Legal / Commerce
Sklash Commerce Terms
Additional terms for merchants using Sklash storefront, catalog, cart, checkout, order, provider, fulfillment, and Commerce hosting features.
Overview
What this means in practice
Explore the systems, responsibilities, and workflows behind this part of Sklash.
Payment evidence
Payment authorization or settlement evidence must be authoritative before an order is represented as actually paid.
Fulfillment is separate
Supplier or Printify fulfillment charges and approval are distinct from customer payment and require their own authorized workflow.
Beta simulations
Controlled beta bypasses must be visibly marked, auditable, and never represented as a real PayPal transaction or real paid entitlement.
Merchant obligations
Sklash provides merchant software; the merchant operates the storefront.
- Ensure products and services are lawful to advertise and sell.
- Provide accurate product descriptions, prices, shipping information, policies, and customer-facing representations.
- Comply with applicable tax, consumer-protection, refund, privacy, product, and marketing obligations.
- Maintain required provider accounts and follow the independent terms of payment, fulfillment, domain, or other connected services.
Payments and orders
An order record and a successful payment are separate concepts.
Sklash may create carts and orders before payment confirmation. An order must not be represented as actually paid merely because checkout was initiated, a return URL was reached, or a beta simulation was used.
Where a payment provider is enabled, Sklash relies on the configured authoritative confirmation or settlement evidence before advancing a real-money order to paid status. Refunds and reversals must remain linked to the original transaction or order event.
Fulfillment approval
Paid status does not automatically authorize production.
Where Sklash integrates with a supplier such as Printify, supplier production may create a separate company-side charge. A paid-and-ready order must pass the configured approval/release workflow before being submitted for production when manual approval is required.
Beta financial controls
Test tooling must remain visibly distinct from real financial processing.
A beta-only merchant or administrator bypass may simulate financial readiness for controlled development and fulfillment testing when the platform explicitly enables that mode. The bypass must be audited and must not create or imply a real PayPal payment, real subscription, cashable user credit, or other real-money entitlement.
Continue
Read the Terms of Service
Commerce Terms supplement the general Sklash Terms.
The general Terms continue to govern accounts, content, hosting, Trust & Safety, third-party services, and beta conditions.