Frequently asked questions

FabSetu is a connected business workspace for Marketplace discovery and sourcing, supplier operations, talent workflows and contact management. One account can participate in multiple products according to your organisation memberships, permissions and product entitlements.

Yes. Public Marketplace pages let you browse published products, approved supplier profiles, categories and public RFQ summaries. An account and an eligible organisation are required for protected actions such as creating RFQs, bidding, ordering or viewing confidential documents.

Create an account and follow the organisation setup flow, or accept an invitation from an existing organisation administrator. Organisation administrators manage membership and product permissions, while FabSetu re-checks active membership on protected requests.

Product visibility and workspace access are different. Your active organisation must have the required product entitlement, and your membership must include the needed permissions. Ask an organisation administrator to review access or switch to another eligible organisation.

Yes. An eligible Marketplace organisation can enable buyer and seller roles and use the workflows allowed by its status and permissions. The organisation remains responsible for separating authorised duties and keeping its public profile accurate.

An authorised seller creates a product in My Products, supplies accurate commercial and technical details, uploads supported assets and publishes it when ready. Only published products from approved, unrestricted Marketplace organisations are eligible for public discovery.

High-risk Marketplace actions can require verified business identity to protect buyers, sellers and payment workflows. PAN and GSTIN verification are kept separate from Marketplace profile readiness, and full identifiers are not shown on public profiles.

An authorised buyer prepares or selects a BOM, describes the requirement, reviews potential bidders and sends the RFQ. Public RFQ pages show only a narrow summary; protected BOM lines, attachments, buyer details and supplier responses remain in authorised workflows.

They are not public. Access is limited to authorised members of the relevant buyer or invited seller organisations and permitted operations users. Organisation IDs supplied by the browser are treated as untrusted and membership is checked on the server.

FabSetu compares declared capabilities such as component support, category, quantity range, region and verification status. Match explanations are discovery signals, not guarantees, so buyers should independently verify technical, commercial and compliance suitability.

Unless an order expressly names FabSetu as the seller, the buyer and seller contract directly. They are responsible for specifications, price, taxes, product compliance, delivery, inspection, warranty and the remedies recorded in their accepted bid, purchase order or other agreement.

Eligible orders can use the configured payment-provider workflow to create and verify payment records. Review the order total, tax and payment status before paying; never share passwords, one-time codes or full payment credentials in messages or support tickets.

Open the relevant order to review its fulfillment status and available dispatch or tracking information. Delivery dates are estimates unless the accepted order makes them binding, and sellers should communicate material delays through the order workflow.

Use the order workflow to request a cancellation before dispatch or to report damaged, defective, short or materially non-conforming goods. Eligibility, evidence and time limits come from the listing, accepted order, seller terms, FabSetu policy and non-waivable law.

Keep the order, payment, carrier, inspection and communication records, then create a Marketplace Support ticket referencing the order and requested outcome. FabSetu can facilitate evidence and platform action, while a commercial ruling may require agreement or a competent authority.

The active organisation controls the workspace, data and permissions used for each protected action. A locally remembered selection improves continuity, but the server re-checks membership and access every time; switching never grants access by itself.

Approved public pages may show organisation descriptions, roles, regions, categories, websites, published products, RFQ summaries and review summaries. Membership records, identity numbers, internal contacts, private certification files, BOMs, bids, NDAs and confidential attachments are not public projections.

Protected operations use server-side authorisation, active organisation context, product entitlements, permissions and tenant-aware data access. FabSetu also uses audit, security and provider safeguards, although no online service can guarantee absolute security.

FabSetu uses authentication and session technology, limited browser preferences such as the active organisation, and first-party operational events for security, reliability and Marketplace analytics. The current application does not deploy third-party advertising cookies or cross-site advertising pixels.

After signing in, open Marketplace Support or the relevant product support area and include the organisation, order, RFQ or error reference. Mark formal complaints as grievances; urgent account compromise, fraud or sensitive-data exposure should be identified clearly for prioritisation.

No. Partner provides supplier-directory operations, while Marketplace owns public supplier discovery, stakeholder capabilities and RFQ matching. They share the FabSetu shell and organisation context but keep their product responsibilities separate.

No. Talent candidate profiles and applications use Talent-specific authorised workflows. Private details such as date of birth, current address and application materials are excluded from public Marketplace projections and unrelated operational summaries.

No. Contacts people, companies, lists, tags and activity are organisation workspace data. A public Marketplace company profile is a separate, deliberately narrow projection and does not expose an organisation's private address book.