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.

Your active workspace is the organisation or personal workspace whose products, data and permissions you are currently using. Its name appears in the application shell. Switch workspaces before starting an action if the record should belong to a different organisation.

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.

Open the Dashboard to confirm the active workspace, review available applications and choose a next action. If an application is locked, check the workspace entitlement and your permissions before contacting support.

A readiness checklist summarises saved information needed for a specific workflow. It helps you see what is complete, what is blocking the next step and what would improve the result. It does not replace approval, entitlement, permission or policy checks performed when you submit an action.

A required item must be completed before the related protected action can proceed. A recommended or optional item improves discovery, matching or profile quality but does not normally block saving. The label beside each checklist item indicates which rule applies.

Readiness is calculated from saved data, not unsaved form values. Save the form successfully, then refresh if the status does not update. Also confirm that you are viewing the same active workspace in which the information was saved.

Dashboard next actions are generated from the active workspace, its enabled applications and your current permissions. They are shortcuts to work you can perform, not assigned tasks or deadlines. Switching workspace or changing access can change the list.

Marketplace uses your organisation state, available navigation and permissions to suggest useful destinations such as completing Settings, reviewing products, opening orders or working with RFQs. Suggestions may change as setup and Marketplace activity change.

Marketplace activation can depend on a complete organisation profile, appropriate Marketplace roles and categories, business identity verification, Marketplace review status, product entitlement and member permissions. Profile completeness alone does not guarantee that every transaction is enabled.

Product readiness checks the current product form for required values such as product name, valid price, stock and valid pricing tiers, while separately identifying useful optional assets and details. Blocking items must be fixed before saving; optional items can be added later.

Talent profile readiness is calculated from saved candidate information. Basic identity and candidate details are marked required, while skills, roles sought and a resume can improve discovery and applications. A resume is optional globally, although an individual job may request one.

Matching readiness indicates whether a job or candidate has enough eligible, saved information for the bounded matching workflow. Candidate visibility and search opt-in also affect searchability. A ready status enables diagnostics; it is not a hiring decision or a guarantee of a match.

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.

Complete the organisation display name, public description, Marketplace roles, at least one contact method, operating regions and categories relevant to the business. Additional capability, certification and facility information can improve discovery when it is accurate and suitable for public display.

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.

A draft is private working data for the seller organisation and can be updated before release. Publishing makes the eligible product discoverable through Marketplace projections, subject to organisation readiness and plan limits. Unpublishing removes it from public discovery without deleting the underlying record.

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.

Invited eligible suppliers can review the protected requirement and respond through the bid workflow. The buyer can monitor responses and continue the sourcing process according to the RFQ state. Keep requirements and attachments current before sending because later changes may require supplier review again.

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.

Lead actions depend on whether the active organisation sent or received the enquiry, the lead's current lifecycle state and the member's permissions. Recipients can progress eligible leads, while resolved or closed states intentionally remove actions that are no longer valid.

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.

Each party sees the actions allowed for its role, the order's current state and its member permissions. A buyer may see payment or receipt actions while a seller may see acceptance, dispatch or fulfillment actions. Operations access does not make private order data public.

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.

FabSetu currently processes orders only when the listed base price is INR 5,000 or less, before product GST, the FabSetu platform fee and the Razorpay fee. For a product above that configurable cap, request an introduction. FabSetu emails both parties their counterparty's organisation, email and phone details, creates no order and processes no payment.

The product detail shows product GST plus a FabSetu platform fee including GST of 2.36% and a Razorpay fee including GST of 2.36%. Review the complete itemised total and accept the transaction notice before adding the product to cart.

After the buyer pays, a FabSetu platform administrator or operator marks the order paid. The seller ships, the buyer confirms receipt, FabSetu operations records settlement to the seller, and an administrator or operator marks the order complete. Operations may initiate a refund under the Platform Terms and Conditions when needed.

No. Shipping and fulfilment remain the responsibility of the buyer, seller and their logistics providers. Keep carrier and inspection evidence. Refunds for payments processed on FabSetu follow the Platform Terms and Conditions and the returns, refunds and cancellation policy.

Return to the order and check its recorded payment status before trying again. Do not assume a browser error means the payment failed, and do not create duplicate payments. If the status remains unclear, contact support with the order and provider reference but no passwords or one-time codes.

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.

Open Talent Profile, complete the required candidate details, choose an appropriate visibility setting and save. Add accurate skills and roles sought to improve job discovery and matching. Readiness uses the saved profile, so unsaved changes are not counted.

The resume is a private candidate-owned asset. Access is provided through short-lived authorised links to permitted Talent workflows, such as an application review; it is not published as a public Marketplace document.

New Talent profiles are public and opted into Candidate Search by default. You can choose private visibility or opt out at any time to exclude your profile from authorised employer search. Applications you deliberately submit remain available to the relevant authorised employer workflow.

Use Find Jobs to browse eligible open roles, save interesting jobs for later, and open a job to review its requirements. When applying, check your profile and any job-specific requirements before submission. Track submitted applications in My Applications.

Open My Applications to view the current employer-managed status and available candidate actions. Withdrawal is available only when allowed by the current application state. If an expected action is absent, the application may already have progressed to a state that does not permit it.

Authorised employer members use Manage Jobs to create and maintain roles for an eligible organisation. Applications and candidate information remain job-scoped, and the actions available depend on the employer workspace, member permissions and application state.

No. Talent matching provides bounded, explainable recommendations from eligible job and candidate information. Employers and candidates should review the underlying requirements and signals; a score is not a guarantee, ranking mandate or automated employment decision.

A new eligible personal workspace starts on the Free plan when it has no persisted paid subscription. Billing shows Free as the current plan, and paid plans remain available as upgrades.

Limits are resolved for the active workspace and checked by the service that owns each action. Monthly actions such as RFQs, enquiries, job postings and networking connects are counted within the current usage period; published-product limits apply to the number currently published, and analytics limits restrict the available history.

The current usage window advances to the next monthly period, so monthly counters are calculated from activity in the new window. Existing records are not deleted. A paid subscription renews according to its billing state; a scheduled downgrade or cancellation takes effect at the recorded period end.

The affected new action is blocked with guidance to review usage or the plan, while existing records remain available according to normal permissions. Monthly capacity becomes available in the next usage period; a higher plan can provide more capacity when an upgrade is available.

A verified paid upgrade is activated immediately. A downgrade is scheduled for the end of the current subscription period so the existing paid access remains in place until then. Billing shows a pending plan change when one has been scheduled.

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 allows one active session per account. Signing in on another browser or device can replace the earlier session. Sign in again only if you intend to make the current browser the active session, and change your password or contact support if you do not recognise the other sign-in.

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.

Contacts keeps people and company directory records inside the active personal workspace. Add or update the company context and relationships that help your team understand the contact, while avoiding unnecessary personal or sensitive information.

Contacts extracts candidate fields such as name, title, email, phone, company, website and address for review. Check the extracted values and any suggested company match before creating records; scanning output can be incomplete and should not be treated as verified data.

Lists organise people for a purpose without creating a second copy of each contact. A person can belong to relevant lists, and list filters help narrow the People view. Deleting a list archives the list but does not delete the contacts it contained.

No. Contacts data is scoped to the active workspace and protected by membership and permissions. Switching workspace changes the records in view; it does not copy or publish people, companies, lists or activity to another workspace.

Members with the required Partner entitlement and supplier permissions can create or update Supplier Directory profiles. Available actions such as editing, archiving or approval depend on the member's permissions and the supplier's current state.

Categories provide the shared classification used by the Supplier Directory and are read-only in the current Partner workspace. Partner settings are available only to members with the supplier-settings permission; neither area replaces Marketplace sourcing or public supplier discovery.

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.