Lore
Merchant of Record vs. Own-Name Selling Trade-off
A platform that lets creators/merchants sell through it typically offers two structurally different contract models, illustrated by ablefy's "Verkauf im eigenen Namen" (own-name selling) vs. "Reseller-Modell" (via ablefy's subsidiary namotto, i.e. a merchant-of-record setup):
- Own-name selling: the seller is the official contracting party — their own AGB/terms, Impressum, and privacy policy apply. The seller needs their own payment infrastructure (e.g. a dedicated escrow/payout account via Stripe or Mangopay, or their own PayPal business account).
- Reseller / merchant-of-record model: the platform or its reseller subsidiary becomes the legal seller of record, using its own terms and handling checkout; the original creator never needs their own PayPal account because payouts are batched (e.g. 1-2x/month, above a minimum threshold) through the reseller.
In both models the original seller still handles direct customer support, correspondence, and cancellations/refunds — the split is purely at the legal/contractual and payment-processing layer, not in customer-facing interaction.
Trade-off axes
- Tax treatment: because the merchant-of-record entity is itself fully tax-liable, individual tax statuses of the underlying seller (e.g. VAT small-business exemption, foreign domicile, recognized-institution exemptions) are NOT passed through — sellers who depend on such exemptions must use the own-name model instead.
- Transaction fees: often structured differently per model — one price may fold in what would otherwise be a separate external payment-processor fee (e.g. PayPal's own cut), making raw percentage comparisons misleading unless you account for fees the other model would incur separately.
- Bookkeeping load: own-name selling generates one invoice per order (higher operational overhead); merchant-of-record consolidates into periodic summary statements (lower overhead), independent of tax status — so even VAT-exempt sellers may still prefer merchant-of-record purely to cut bookkeeping work.
- Recurring/automatic payments: counter-intuitively, subscriptions and installment auto-debits can be MORE reliable under merchant-of-record, because they ride on the reseller's already-approved, high-volume payment account, whereas an individual seller's own PayPal account must clear PayPal's own risk/approval criteria (payment history, low dispute rate) before recurring billing is enabled.
- Product/white-label restrictions: own-name selling permits full white-labeling (seller's name on the invoice) and physical goods; merchant-of-record models typically restrict physical products sharply (e.g. books only) because the reseller entity bears legal/logistics liability for what it resells.
- Policy control: own-name selling lets the seller set their own cancellation/return terms (with the seller bearing legal responsibility for their validity); merchant-of-record imposes standardized terms, changeable only in exceptional, vetted cases.
Switching between models after launch is typically costly/complex, making this an early, largely one-way structural decision rather than something to defer.
This pattern generalizes beyond ablefy: any platform offering both a direct-merchant path and a merchant-of-record/reseller path (App Store vs. own billing, Paddle/Gumroad-style MoR vs. direct Stripe integration) faces the same tax-pass-through, bookkeeping, recurring-payment-reliability, and product-category trade-offs.