How to create a partner ticket correctly

Instructions for filling out a partner ticket so that your request is processed quickly and properly prioritized.

Updated at May 13th, 2025

+ More

Table of Contents

Why read this guide? Step-by-step instructions for creating a ticket Choose the right category Fill in the basic fields Fill in the additional fields per category Attach clear evidence Basic fields (required) Additional fields (visible depending on the selected category) Summary Keywords

Why read this guide?

A well-filled ticket speeds up processing, reduces back-and-forth questions, and ensures that the most important requests get the attention they deserve.

Step-by-step instructions for creating a ticket

Choose the right category

Select Bug , New Feature , Enhancement or Question . The correct category ensures the correct owner of the ticket and the SLA time.

Fill in the basic fields

Write a concise Title and Short Description , set a Desired Deadline and describe the Business Impact . Always include your contact information and any necessary attachments.

Fill in the additional fields per category

Bug: Steps to reproduce, current and expected result, environment (prod/staging + browser), severity.
New feature / Improvement: User story, benefit / KPI, boundaries, mockup / API spec and acceptance criteria.

Attach clear evidence

Add images, videos or logs that illustrate the problem/need. The clearer the material, the faster the ticket will progress.

Basic fields (required)

Title – 1 sentence summary
Short description – 2–3 sentences
Category – Bug / New feature / Improvement / Question
Desired deadline – dd.mm.yyyy
Business Impact – What will change if this is implemented/fixed?
Contact person (Slack)
Attachments – images, logs, videos, etc.

Additional fields (visible depending on the selected category)

Bug

Steps to repeat – step 1, step 2…
Current result
Expected result
Environment – prod/staging, browser version, device
Severity – Blocker / Major / Minor / Trivial

New feature / Improvement

User Story – “As a user, I want to … so that …”
Benefit / KPI – e.g. +2% AOV
Limitations – what is NOT included
Mockup / API spec (link)
Acceptance criteria

Summary

By carefully filling out the template above, you ensure that AI Commerce team can properly prioritize your ticket and move forward with a resolution without unnecessary delays.

Keywords

partner ticket
ticket template
bug report
new function
improvement
AI Commerce support
prioritization
Control panel tickets
Akeneo integration
ticket template

partnership creating ticket