Internal Notes

Internal notes are a powerful tool for managing how your listings behave across marketplaces. You can find the internal notes field by clicking on any listing to open the quick edit box.

Our team refers to internal notes during the fulfillment process. If a listing has an email address in the internal notes field and a corresponding login saved in Lysted, our team will take responsibility for fulfilling that sale.

If you're set up on automation but need to add a listing manually for any reason, make sure the proper internal note and login are in place — both are required for our team to handle fulfillment on your behalf

Important: For our team to take responsibility for fulfillment, each listing must have an internal note with the account the tickets are located in. An accurate login for that account must be saved in Settings → Logins, and email forwarding must be enabled. Any sale without the proper internal note is your responsibility to fulfill.

If there is no internal note, we will assume you are fulfilling the order yourself.

If you are using the SecureMyPass integration to generate transferless links for fulfillment, add one of the following notes to your listing:

Because Ticketmaster does not accept wallet links, always pair either note with NOTNOW.

Example: SMPWALLET NOTNOW or SMPMANUALBIND NOTNOW

For full setup instructions, see the Secure My Pass Integration article.

In addition to fulfillment, internal notes support specific codes that allow our system to make per-marketplace adjustments to a listing. You can use them to:

Use these codes to post a listing on one specific marketplace and remove it from all others.

Example: +tmplus will post the listing on Ticketmaster+ only and remove it from all other marketplaces.

Use these codes to remove a listing from one specific marketplace while keeping it live everywhere else.

Example: NOSTUB will remove the listing from StubHub but keep it live everywhere else.

Use these codes to customize the section name displayed on each marketplace.

Example: @secsh[General Admission Floor] @secvg[General Admission Floor] @secvs[Floor GA] will display "General Admission Floor" on StubHub and "Floor GA" on Vivid Seats.

Note: When updating the section on StubHub, use both @secsh[new section] and @secvg[new section] to ensure both StubHub and Viagogo are updated.

Use these codes to customize the row displayed on each marketplace.

Example: @row[11] will list the row as Row 11 on all marketplaces. This is commonly used to mask seat locations for season ticket holders.

Note: AXS Resale is not included in this table. AXS tickets are delivered via API and do not support section/row customization through internal notes.

Use these codes to adjust pricing on specific marketplaces by either a dollar amount or percentage of your list price in Lysted. These notes override Lysted's default markup.

Example: @VS%[5] @SH$[5] @SG%[-5] will increase the price on Vivid Seats by 5%, increase the price on StubHub / Viagogo by $5, and decrease the price on SeatGeek by 5%.

Use these codes to control how many days before the event or in-hand date automation will attempt to fulfill.

Examples:

Note: Sync will automatically override any fulfillment date notes 72 hours before the event. If you need to prevent automatic fulfillment entirely, add NEVERFULFILL to the listing's internal notes.