Byfluence ERD

A concise, high-level view of the core entities and relationships that power the Byfluence platform. Use this as a guide when building features or integrating with the API.

Diagram

100%
Byfluence ERD Diagram

Domain Overview

Shops & Sellers

Entities for shop profiles, verification, and seller metadata.

  • Seller (Shop profile, verification)
  • SellerSocial (links)

Physical Products

Catalog, variants, visibility, inventory, and marketplace listings.

  • SellerProduct (authoritative listing)
  • BaseProduct, Category, Property
  • RetailedProduct, MarketplaceListing

Wallet & Payments

User and platform wallets, transactions, top-ups, payouts, and bank accounts.

  • Wallet, Transaction
  • PayoutBankAccount
  • TopUpRequest, PayoutRequest

Customer Relationships

Following, buyer–seller linkage, and engagement.

  • Follow, BuyerSellerRelationship
  • Review, Rating (where applicable)

Key Entities

Seller
referenceId, shopName, verificationStatus, tinNumber, vatNumber, createdAt, updatedAt
SellerProduct
referenceId, sellerId, name, description, sellingPrice, stock, visibility, categoryId
Wallet
referenceId, ownerUserId, currency, availableBalance, lockedBalance, totalEarned
Transaction
referenceId, walletId, amount, type, sourceType, isLocked, createdAt

Core Relationships

  • Seller 1 — n SellerProduct: a shop can publish many seller products.
  • Category 1 — n SellerProduct: products belong to a single category.
  • User 1 — 1 Wallet: each user owns one primary wallet (additional types optional).
  • Wallet 1 — n Transaction: wallet accrues many transactions.
  • User 1 — n PayoutBankAccount: multiple payout destinations per user.

Conventions

  • referenceId: stable, externally visible identifier (e.g., ByF-SELL-PROD-XXXXXX).
  • Soft-visibility for products: Public | Hidden | Private.
  • Timestamps: ISO-8601 in UTC, fields include createdAt and updatedAt.
  • Money: store as integers (minor units) or precise decimals depending on module; API outputs formatted strings.