SquidSupport
Product reference / Supplier Tickets

Supplier Tickets

In the app: Supplier Tickets

Needs the 'View Supplier Tickets' permission.

Supplier Tickets lists every request your organization has made to the supply side: the suppliers and fulfilment partners who ship your orders. The AI files these requests while it handles a customer's ticket, and your team can file them by hand. This page is where staff follow them up.

What a supplier ticket is

A supplier ticket asks a supplier to do or answer something, usually about one order: cancel it, change it, find its tracking, explain a failed delivery. It has a subject, a category, a priority, a due date, assignees and a thread of comments.

Where a ticket goes depends on the supplier, which is set under Settings → Suppliers:

  • A supplier on the Supplier Portal gets the ticket in the portal. Eligible active assignees receive a notification in Squid or in the portal. Emails wait for background delivery. The supplier answers in the portal, and the answer appears in the ticket's thread.
  • A supplier still on Basecamp gets a Basecamp to-do. While suppliers move over, open Basecamp to-dos are listed here as well, read-only: they open in Basecamp and cannot be selected or edited here. A to-do leaves this list once Squid has seen that it was completed or removed in Basecamp.
  • An internal supplier is your own supply-chain staff. No outside login sees the ticket.

While the Supplier Portal is turned off for the organization, new order requests go through Basecamp even for suppliers configured for the Portal. General threads still stay in Squid.

A general thread is a ticket without an order and without a customer conversation, for things like holiday closures, stock updates or process questions. The AI never reads a general thread and it never leads to a message to a customer.

Notifications and the AI follow-up belong to tickets that were made while the Supplier Portal was turned on in Settings. On a ticket without it, for example a general thread started while the portal was off, or a ticket that was already completed when the portal was turned off, a comment only notifies the people mentioned in it.

The link "Supplier Tickets" in the navigation is hidden for people without the 'View Supplier Tickets' permission. A teammate with access to some stores only sees the tickets of those stores.

Views, search and filters

The view tabs choose which tickets are listed:

  • "All open": every ticket that is not completed. This is where the page starts.
  • "Assigned to me": open Portal tickets you are an assignee of.
  • "Unassigned": open Portal tickets with no assignee. Basecamp to-dos are never listed here, because Squid does not know who they are assigned to.
  • "Overdue": open tickets whose due date is before today. A ticket that is due today is not overdue yet; it moves to "Overdue" the next day.
  • "Due today": open tickets whose due date is today.
  • "General threads": open general threads only. A completed general thread is under "Completed".
  • "Completed": completed Portal tickets. Basecamp to-dos are never listed here.

"Today" in "Overdue" and "Due today" is the date in UTC, not in your own timezone, so a ticket can change tab a few hours before or after your midnight. A ticket without a due date is in neither tab. Basecamp to-dos have no due date in Squid, so they never appear in "Overdue" or "Due today", whatever their date is in Basecamp. The number on each tab counts the tickets that match the tab together with the search and the filters you have set.

The search box searches the order number, the subject, the ticket's reference, and the name and email address of the customer in the linked conversation.

Sort: "due date (soonest)", which is the default, or "last activity (newest)". Sorted by due date, tickets without a due date come last, and urgent tickets come before normal ones on the same date.

Rows per page: 25, 50 or 100. The default is 25.

"Columns" chooses what the table shows: order, supplier, store, category, source, priority, due date, assignees, last activity and destination. The subject is always shown. Category and source are not columns of their own; they are labels under the subject. The choice is not remembered when you leave the page.

Filters, each a menu, can be combined:

  • "Priority": urgent or normal.
  • "Category": cancellation, modification, tracking, incomplete or failed delivery, unauthorized order, wrong item sent, pre-sale, reshipment, POD request, similar item, returned to sender, other, or general thread. A category also finds the tickets of its dispute variant.
  • "Source": who filed the ticket. "AI", "Agent" (a teammate), "System", or "Supplier (general threads)" for general threads a supplier started.
  • "Store" and "Supplier". "Supplier" also offers "No supplier (deleted)". A teammate with access to some stores is only offered those stores and their suppliers.
  • "Destination (ticket's system)": "Portal tickets" or "Basecamp to-dos (read-only)".

"Clear filters" removes them all, empties the search box and goes back to "All open" sorted by due date. The number of rows per page stays.

Ticket list

Each row is one ticket. Clicking its subject opens the ticket. A Basecamp row has a lock, and its subject opens the to-do in Basecamp instead when its external link is available.

The columns:

  • Order: the order number, when the ticket is about an order, with the first characters of the ticket's reference under it.
  • Subject: what is asked. For a Basecamp to-do it is made up of the reason, the store and the order number.
  • Category and Source: the kind of request and who filed it, as labels under the subject. The source reads "ai", "agent", "system" or "supplier".
  • Supplier: the supplier the ticket is with. "Internal" marks an internal supplier. "No supplier (deleted)" means the supplier was removed after the ticket was made.
  • Store: the store the order belongs to.
  • Priority: "Normal" or "Urgent" with a flag. A Basecamp to-do always shows "Normal".
  • Due date: the date the supplier should have answered by. It turns red with "Overdue" on an open ticket from the day after the due date, counted in UTC.
  • Assignees: the people the ticket is assigned to, or "Unassigned". They can be teammates and the supplier's own users. A Basecamp to-do shows a dash, because Squid does not know its assignees.
  • Last activity: the later of the last change to the ticket and its last comment.
  • Destination: "Portal" or "Basecamp".

Under the table: how many tickets are shown out of the total, and buttons for the previous and next page.

Empty and error states:

  • "No supplier tickets yet" when "All open" is empty and no search or filter is set. It also shows when every ticket is completed.
  • "No tickets match these filters" when another view, the search or the filters leave nothing. Other tickets may exist outside them.
  • Both show "Raise the first ticket" to people who can create tickets.
  • "Couldn't load supplier tickets" with "Try again" when loading failed. Your filters are kept.

Bulk actions

Needs the 'Manage Supplier Tickets' permission.

Tick the checkbox on one or more rows, or the one in the table header for all Portal tickets on the page, to open the bulk bar. The checkboxes are only there for people with the 'Manage Supplier Tickets' permission. Basecamp rows cannot be selected.

  • "Complete" marks the selected tickets as completed.
  • "Reopen" makes completed tickets open again. The supplier's side is notified when the ticket still has Portal notifications enabled.
  • "Reassign to…" replaces all assignees of the selected tickets with the one person you pick. Eligible active recipients are notified when the ticket still has Portal notifications enabled. Teammates are always offered. The supplier's users are only offered when every selected ticket is with the same supplier.
  • "Clear" drops the selection.

A bulk action changes all selected tickets or none: if one of them cannot be changed, nothing is saved and the page shows the reason. Every change is recorded in each ticket's activity. A bulk action never sends a message to a customer, and completing tickets in bulk does not start the AI follow-up.

New supplier ticket

Needs the 'Create Supplier Tickets' permission.

"New ticket" files a request about an order, and "General thread" starts a general thread. Both need the 'View Supplier Tickets' and 'Create Supplier Tickets' permissions in this dialog. A person with only 'View Supplier Tickets' can read tickets but cannot create, comment on or edit them.

The dialog has two tabs, "Order ticket" and "General thread", so you can still switch. A general thread has no order number, category or priority field. The fields:

  • "Store": the store the order belongs to. Required. Only stores that have a supplier are offered.
  • "Order # (optional · free text)": the order number, at most 100 characters. When Shopify knows the order, Squid shows the supplier that the store's routing would pick and selects it, unless you already chose a supplier yourself.
  • "Category": the kind of request, "Modification" to start with. The list also has the dispute variants. It decides which supplier handles the ticket and who is assigned by default.
  • "Priority": "Normal", the default, or "Urgent".
  • "Supplier": required. Each option says whether it is on the Portal or on Basecamp, and whether it is internal. With the Supplier Portal turned on, an external supplier's unsupported categories and pre-sale requests go to the internal supplier. For a supplier shown as Portal, the dialog warns about this and blocks creation if no internal supplier is configured. A Basecamp supplier with no internal supplier keeps using Basecamp routing. A Basecamp supplier with an internal supplier can also be rerouted, even though the dialog does not show that warning. For a Basecamp destination, the button reads "Create Basecamp to-do". Explicit assignees must have matching users in the Basecamp project, or creation is refused.
  • "Subject": required, at most 500 characters. For an order ticket it is filled in from the category, the store and the order number, and you can change it.
  • "Due on": the date an answer is due. It starts on tomorrow. If you empty it, a Portal ticket still gets tomorrow as its due date.
  • "Assigned to (optional)": teammates or the supplier's users. The supplier's default assignees for the category are ticked to start with. If nobody is ticked, a Portal ticket still gets those default assignees.
  • "Details (optional)", or "Message" on a general thread: the text of the request.
  • Attachments: up to 10 files; images, PDF, CSV and XLSX, up to 10 MB each. If the ticket is created and a file fails to upload, the button changes to "Retry uploads" so the ticket is not created twice.

The button reads "Create ticket", or "Start thread" for a general thread.

A ticket made from a customer conversation in the Inbox is linked to that conversation, and the AI picks up the supplier's replies there. The conversation must belong to the same store as the ticket.

Duplicates. For an order ticket with an order number, Squid checks for an open ticket or Basecamp to-do of the same store, order and kind of request. When there is one, the dialog says so and offers "Open ticket", "Add as comment" and "Create anyway". "Add as comment" adds your details, or the subject when you wrote none, to the open ticket instead of making a new one. A second ticket would split the supplier's replies. General threads are not checked.

Creating a Portal ticket queues notifications for eligible active assignees when the ticket was created with the Supplier Portal turned on. Emails wait for background delivery. It does not message the customer.

When no supplier can take a ticket yet, the dialog points to Settings → Suppliers, where a store is assigned to a supplier.