SquidSupport
Product reference / Settings

Suppliers

In the app: Settings → Suppliers

Needs the 'General Settings' permission.

A supplier is whoever fulfils your orders. This page lists your suppliers, the stores each one works for, where tickets about their orders go, and the address customers send returns to. Suppliers are shared by the organization: one supplier can be assigned to any number of stores.

Supplier list

Each row shows:

  • "Supplier": the name, and under it the Shopify fulfiller names linked to it, or "No fulfiller names".
  • "Assigned stores": the stores the supplier works for, or "Unassigned".
  • "Tickets go to": "Basecamp" or "Portal", "since" with the date of the last switch between the two, and "Internal" for an internal supplier.
  • "Reasons handled": how many kinds of ticket the supplier takes, with dispute variants counted together with their ordinary reason. The total excludes general threads. "Inherit routes" means the selection follows its Basecamp routes.
  • "Slack channel": the linked channel and its state, or "Not linked".
  • "Portal users": the names of the active portal logins linked to the supplier, "Staff members" for an internal supplier, or "No active portal user".
  • "Language": English or simplified Chinese.
  • "Return address": the supplier's own return address, or "Store fixed address" when it has none.

The "since" date, the Slack channel, the portal users and the inherited reason count are only filled in while the Supplier Portal is turned on. While it is off, the row shows "Not linked", "No active portal user" and, for a supplier that inherits its reasons, a count of 0.

The buttons on a row are "Tickets & routing", edit (pencil) and delete (bin). Deleting asks for confirmation and cannot be undone. It removes the supplier together with its fulfiller names, its store assignments, its Basecamp routes, its default assignees, its Slack channel link and its links to portal logins. A store that had it as default supplier goes back to "Our own team". Tickets that were already filed are kept.

Warnings appear above the list while the Supplier Portal is on. A supplier whose tickets go to the portal and that has nobody to receive them shows "No active portal user. Tickets are created but nobody is emailed.", with a "Manage recipients" button that opens its "Default assignees" tab. For an outside supplier that means no active portal login is linked to it; for an internal supplier, that no active teammate is ticked under "Default assignees". A supplier whose Slack bot was removed from its channel shows "Bot removed. Re-add the bot to resume Slack sync.", with a "Fix channel" button that opens its "Slack" tab.

"Add supplier" opens an empty supplier. When there are none, the page shows "No suppliers yet" with "Add your first supplier".

Add or edit a supplier

"Add supplier" opens the "Add supplier" dialog; the pencil opens "Edit supplier". Nothing is saved until you click "Create" or "Save".

"Supplier name" is required, up to 100 characters.

"Shared return address" is on for a new supplier; for an existing one it is on when the supplier has an address. When it is on, fill in the supplier's own return address: "Street + street number", "City" and "Country" are required; "Company", "Contact person", "Telephone", "Zipcode" and "Region" are optional. This address is given for the items this supplier fulfils and overrides the store's fixed return address. Turn it off for a supplier that does not take returns: returns then go to the store's fixed return address, and the supplier and its ticket routing stay in place. A supplier's own address also appears in the "Fixed return addresses" table further down.

"Assigned stores": tick every store this supplier fulfils orders for. A supplier can only be chosen as a store's default supplier when it is assigned to the store. Unticking a store that has this supplier as its default supplier sets that store back to "Our own team".

A new supplier starts with its tickets going to Basecamp, in English, with reasons inherited from its Basecamp routes. Change those under "Tickets & routing" on its row.

A teammate whose account is limited to certain stores can change or delete a supplier only when every store it is assigned to is one of theirs. A supplier that also serves other stores, or that has no store at all, cannot be changed by them, and a supplier they add must be assigned to at least one of their stores.

"Shopify fulfiller names": the names Shopify shows as the fulfiller of an order. Type a name and click "Add" or press Enter; the cross removes one. Squid uses them to work out which supplier a product on an order belongs to. A fulfiller name is matched first against these names, then against a supplier whose own name equals the fulfiller name; in both cases only suppliers assigned to the order's store are considered. Upper and lower case do not matter. A fulfiller name can belong to one supplier only in the organization.

For a supplier ticket, the supplier is worked out per product, from the order's own shipments:

  • the fulfiller that shipped the product, when the shipment names it;
  • for a product no shipment names, the order's only fulfiller of physical items, provided none of the physical shipments was marked by hand;
  • when the order does not say, the supplier that shipped the same product on the store's most recent shipped orders, if those all point to one supplier;
  • the store's default supplier, when the order names no fulfiller of physical items at all;
  • otherwise no supplier: the ticket stays on your own team's route.

Add-ons that need no shipping, such as shipping protection, are never used to pick a supplier, and neither is a shipment a teammate marked by hand in Shopify.

For a return address, the AI looks only at the order itself: the fulfiller that shipped the product, or the order's only fulfiller. It does not look at recent orders or at the default supplier. When that gives no supplier, or a supplier without an address of its own, the customer gets the store's fixed return address.

A supplier can also carry an older "default" mark from before the "Default supplier" table existed. This page does not show or change it. Where a store has such a supplier assigned, a fulfiller name that matches no supplier resolves to it.

Tickets and routing

"Tickets & routing" on a row opens "Edit" followed by the supplier's name, with four tabs.

"Tickets & routing" tab:

  • "Tickets go to": "Basecamp" or "Supplier Portal". With Basecamp, tickets for this supplier are filed as Basecamp to-dos, routed under Settings → Basecamp. With the Supplier Portal, they become tickets the supplier answers in the portal. The portal button is disabled until the Supplier Portal is turned on in Settings; while it is off, new requests that use this routing go to Basecamp whatever is chosen here. Existing portal tickets keep their portal workflow, and staff can still create portal-only threads.
  • "Internal supplier (staff only, no supplier logins)": tickets go to your own staff and no outside login is involved. An organization can have one internal supplier. A supplier that still has portal logins or outside assignees cannot be marked internal; remove those first.
  • "Language": "English" or simplified Chinese, the supplier's language. Slack ticket labels and automated status messages use it; comments keep their original text. Ticket emails to a portal user who has no language of their own also use it.
  • "Reasons handled": the kinds of ticket this supplier takes. "Inherit current Basecamp routes" follows the reasons the supplier has a Basecamp route for in the stores it is assigned to; untick it to choose reasons by hand, starting from the inherited ones. For an outside supplier, saving an empty selection sends its tickets to the internal supplier, subject to the exception below when none is configured. An internal supplier keeps its own destination regardless of its reasons.

Reasons only change where a ticket goes while the Supplier Portal is turned on. A ticket with a reason the supplier does not handle then goes to the internal supplier, and so does every pre-sale question. Without an internal supplier, a supplier on Basecamp keeps its Basecamp routes, and a supplier on the portal cannot be given a ticket with a reason it does not handle: creating it fails with a message to set up an internal supplier first.

The list has no boxes for the dispute variants of a reason, such as a cancellation on a disputed order. A dispute variant counts as handled only when it was among the inherited reasons at the moment you unticked "Inherit current Basecamp routes"; ticking a reason by hand does not add its dispute variant. Unticking all the visible boxes does not remove inherited dispute variants, so the selection may still handle those tickets.

"Save" stores the tab and closes the dialog. Only what you changed is saved, and each change is written to "Change history".

Switching to the portal. Choosing "Supplier Portal" opens "Switch [supplier] to the Supplier Portal?" before anything changes. "Cancel" there closes the whole dialog without saving. It shows four checks, each with "Done" or "Not yet":

  • "Named, active users who have signed in at least once": at least one active portal login linked to this supplier has a name, has signed in and has set their own password. For an internal supplier the check is instead that its fallback list under "Default assignees" has at least one active staff member.
  • "One-page guide received": nothing checks this for you. Click "Mark as sent" once the supplier has the guide; that is saved at once and written to "Change history".
  • "Language set": the supplier has a language. Every supplier starts with English, so this is done from the start.
  • "Slack channel connected and tested (if used)": done when no Slack channel is linked. With a linked channel, the channel must be connected and a test message must have been delivered since it was linked.

When all four are done, "Switch to Portal" is enabled. When not, "Override the gate (settings access required)" lets you switch anyway: type why you switch now and click "Override and switch". The reason and the state of the checks are recorded under "Change history" with your name and the time. The override needs the 'General Settings' permission, which everyone who can open this page has.

The switch changes where new tickets go and moves nothing: after it, new tickets from the AI and from staff go to the portal, and Basecamp to-dos that are already open finish in Basecamp. Switching back to Basecamp has no checks: new tickets go to Basecamp and open portal tickets are finished in the portal.

"Default assignees" tab: who a new portal ticket is assigned to. Pick a "Reason", tick the people and click "Save assignees". Each reason has its own list, saved on its own and written to "Change history". For an outside supplier you can tick your own staff and the supplier's active portal users; for an internal supplier only staff. Everyone ticked must be active when you save.

How Squid picks the assignees of a new ticket:

  • Outside supplier, people ticked for the reason: the ticked people who are still active. A portal user must also still be linked to the supplier.
  • Outside supplier, nobody ticked for the reason: every active portal user linked to the supplier.
  • Internal supplier, people ticked for the reason: the ticked staff who are still active.
  • Internal supplier, nobody ticked for the reason: the staff ticked under "Fallback (all reasons)".

"Fallback (all reasons)" can only be saved for an internal supplier. The menu also offers it for an outside supplier, but saving it there fails; an outside supplier already falls back to all its active portal users.

"Slack" tab: link one Slack channel to the supplier. It needs the Supplier Portal turned on and Slack connected under Settings → Integrations.

  • "Channel": choose a channel from the connected workspace, or a Slack Connect channel shared with the supplier, and click "Save channel". Invite the Squid bot to the channel first: a channel without the bot is listed with "bot removed" and will not receive anything. A channel can be linked to one supplier only. "Portal and email only" removes the link. "Revert last save" puts the previous choice back.
  • What is posted: each new portal ticket for the supplier becomes a message in the channel, in the supplier's language, with its subject, store, order number, priority, due date, status, assignees and the names of its attachments, and buttons to open the ticket, complete it and reopen it. Later comments, changes and attachments are posted as replies under that message.
  • Customer contact details: before posting, Squid replaces the customer's known email address, phone number and address lines, and anything written like an email address, an international phone number or a street address, with "[redacted]". The phone-pattern filter keeps numbers that match known order or tracking numbers. This is a text filter: contact details written in a form it does not recognise are posted as written.
  • What comes back: a reply under the ticket's message in Slack becomes a comment on the ticket. Squid matches the Slack user to a portal user or a teammate by email address; anyone it cannot match is shown as their Slack name followed by "via Slack". Anyone in the channel can use the complete and reopen buttons.
  • Linking does not replay history: tickets and comments from before the link are not posted. An older ticket appears in the channel when something new happens on it.
  • Status line: the channel name, "Slack Connect" or "Workspace channel", its state, and "Tested" or "Not tested". When the channel is archived, the bot is removed or Slack is disconnected, posting stops and messages that were waiting are dropped; tickets continue in the portal and by email, and your team gets one notification. After you fix and relink the channel, only new events are posted.
  • "Send test message" queues a test message to the channel; it is available while the channel is connected. Click "Refresh status" after it arrives: the status then shows "Tested", which the portal switch check needs. Linking another channel, or a channel that stops working, resets it to "Not tested".

"Change history" tab: the supplier's routing changes, oldest first, with who made each one and when: where tickets go, internal supplier, language, reasons handled, default assignees, the guide being marked as sent, an overridden switch with its reason, and a Slack channel being linked. Changes to the supplier's name, address, stores and fulfiller names are not listed, and neither is removing the Slack link.

Default supplier

"Default supplier" has one row per store with a menu under "Unshipped-order tickets go to". The section is hidden when the organization has no stores.

The default supplier is used when Squid cannot tell from the order who fulfils a product: the order names no fulfiller of physical items, for example because nothing has shipped yet, and the store's recent shipped orders of the same product do not point to one supplier either. See "Shopify fulfiller names" for the full order.

  • "Our own team" is the starting value. The ticket then stays on your team's own route.
  • A supplier: only suppliers assigned to that store can be picked. A store without an assigned supplier offers "Our own team" only, and a note under the table says how many stores that applies to.

A choice is saved as soon as you make it, and the message confirms where that store's tickets now go. It applies to tickets filed from then on.

For a ticket that goes to Basecamp, the chosen supplier still needs its own Basecamp route for the ticket's reason, under Settings → Basecamp. Without one, Squid tries the "All suppliers" route. If no suitable route exists, filing the ticket fails.

Fixed return addresses

A fixed return address is a store's default address for customers to send returns to. The AI gives it to a customer for an item when it cannot tell from the order which supplier shipped the item, or when that supplier has no return address of its own. Without any address, the AI cannot tell a customer where to send a return.

The table shows each address, the stores that use it under "Used by stores" ("Unassigned" when none), and the stores it is the dispute address for under "Dispute address for". The address a supplier has as its own is listed here too, as "Unassigned" unless you also give it to a store.

A store with no fixed address here still uses an older free-text return address if one was saved for it before this table existed.

"Add address" opens "Add fixed return address"; the pencil opens "Edit fixed return address".

  • Address fields: "Street + street number", "City" and "Country" are required; "Company", "Contact person", "Telephone", "Zipcode" and "Region" are optional.
  • "Used by stores": the stores this is the everyday return address for. Each store can use only one fixed return address; a store that already has one is disabled and marked "(assigned to another address)".
  • "Dispute / escalation address for stores": the stores for which this is the address the AI gives customers who are on the dispute or legal track, when its instructions say to. It is then given for every item, whichever supplier shipped it. A store can have one dispute address; a store that already has one is disabled and marked "(dispute address set elsewhere)". For a store without one, the AI gives the usual address: the supplier's own, or else the store's fixed return address.

The bin deletes an address after you confirm; its stores then use supplier return addresses, or an older free-text return address if one is still saved for the store. An address that a supplier still uses as its own cannot be deleted: the page then shows "Failed to delete fixed return address". Turn off "Shared return address" on that supplier, or change its address, first.

Supplier Logins

Logins let people at a supplier sign in to the supplier portal and see their tickets. One login can be linked to several suppliers, across stores. An internal supplier cannot be linked to a login.

The table shows each login's name, email, linked suppliers and status: "Active" or "Inactive", plus "hasn't set a password yet" for an active login whose owner has not chosen a password yet.

"Add login": enter a name and an email address, both required, and tick the "Linked suppliers". An email address can have one login. Squid emails that address a link to set their own password; the link works for 7 days. You are never shown a password to pass on. A dialog then says whether the email was sent and when the link expires. The email is queued for sending: a successful result can mean the send was queued, rather than delivered to the supplier. This also applies to "Resend invite" and "Reset password". If the email could not be sent, the login still exists; use "Resend invite".

On a row:

  • Edit: change the name, the linked suppliers and "Active". The email address cannot be changed. An inactive login can no longer sign in and is signed out at once.
  • "Resend invite": emails a new link to set a password, valid for 7 days. Nothing else changes: the current password keeps working and nobody is signed out.
  • "Reset password": after you confirm, the current password stops working, the person is signed out everywhere, and they are emailed a link to set a new one. If that email cannot be sent, the old password has still stopped working; use "Resend invite".
  • Delete: removes the login after you confirm. This cannot be undone.