Skip to main content
Sellfern includes a support ticket system for reporting issues and requesting features. You can attach screenshots, set priority, and follow progress through comments without leaving the app.

Creating a ticket

1

Navigate to Support

Click Support in the main sidebar to see your submitted tickets.
2

Click New Issue

Click New Issue in the ticket list to open the submission form.
3

Fill in title and description

Write a short required title and a detailed required description. Include steps to reproduce, what you expected, what actually happened, and any visible errors.
4

Select a related page

Optionally choose the page or feature involved, such as Dashboard, Order Ingestion, Analytics, or Listing Studio.
5

Set priority

Choose a priority based on impact.
6

Attach screenshots

Upload up to 5 screenshots. Supported formats include JPG, PNG, GIF, and WebP.
7

Submit the ticket

Click Submit Issue. Sellfern redirects you to the ticket list and shows a confirmation notification.

Ticket statuses

Adding comments

Use comments to communicate with the support team from inside a ticket.
  1. Open the ticket from your list.
  2. Scroll to the comments section.
  3. Type your message.
  4. Press Enter or click Send.
Comments include the user’s email, role, and timestamp.

Tips for good bug reports

Clear reports get resolved faster.
  • Be specific about the page and action. Describe exactly where you were and what you were doing.
  • Attach screenshots or screen recordings. Visual evidence helps show what went wrong.
  • Include relevant identifiers. Add order IDs, SKUs, store names, or supplier names when relevant.
  • Note your browser and OS. For example, Chrome on macOS or Edge on Windows.
Admins can view all tickets submitted by users in the organization. Regular users can only see tickets they submitted themselves.
Deleted tickets cannot be recovered. If you delete a ticket by mistake, submit a new one.

Developer support

For questions about public integrations, include the relevant request ID, endpoint from the API Reference, timestamp, and organization context when opening a ticket. Do not include secrets or private keys in ticket text or screenshots.