FAQ
No. Sentrick is a B2B marketplace, workflow, and records platform. Suppliers are the sellers and remain responsible for their products — identity, composition, labeling, quality, conformity, recalls, and warranties.
Qualification is a listing gate. A product lists only after an approved exact revision, current accepted evidence, an active supplier and subscription, acknowledged liability, market approval, and no holds. It is not a Sentrick guarantee of the product.
Subscriptions for buyer/supplier/logistics access, a marketplace commission (fee schedule to be published) on product orders (computed server-side), and separate advertising fees for logistics. These revenue types are never mixed.
A buyer approver — a role distinct from the person who created the RFQ. This separation of duties is enforced by the server, not just the interface.
Payment is initiated by the buyer and recognized only via a verified webhook; capture posts a double-entry ledger exactly once. Totals and the marketplace commission are calculated server-side from the immutable order record.
Returns and disputes proceed in separate, auditable stages. Receiving returned goods does not approve a refund. Responsibility is decided only by authorized Sentrick roles with evidence and a recorded reason.
No. The logistics network is advertising and directory only. Sentrick takes no freight commission and is not a carrier, broker, forwarder, or insurer.
Not directly. Sentrick does not perform customs clearance, hold a customs broker licence, employ customs brokers, or act on their behalf. It displays the services of independent Customs Clearance & Brokerage partners — customs clearance, licensed customs brokerage, import/export documentation, import duty, HS-code and trade-compliance support, duties & tariff guidance, and port/airport clearance — who advertise on the platform, so buyers and suppliers can find a suitable partner. Partners pay a subscription, directory fee, featured placement, or sponsorship — never a commission on clearance.
Yes. Tenant data is isolated at the database with row-level security, and user-facing reads run through a non-privileged role so one organization cannot see another's data.