Back issues usually live in a custom post type with fields for title, issue number, grade, variant, and price. SleekAI reads those through the data-source wizard and quotes them in chat. Grade can be ungraded staff-assessed or CGC slabbed, and both flow through to the bot's answer. For shops still using a spreadsheet, the recommendation is to move that data into a CPT first because that is what every other tool in the workflow (search, filters, the chatbot) reads.

Yes, if pull lists are stored as a CPT or as ACF data tied to the WordPress user. For a logged-in customer, the bot can answer 'what is on my pull list', 'add Daredevil 1 to my list', and 'how much do I owe this week'. The display-condition system supports logged-in role checks so anonymous visitors never see another customer's pull list. The actual addition can be a link to the standard form or a direct REST call depending on your dev capacity.

If you maintain a weekly new-releases event or post (most shops do, for the newsletter), SleekAI reads it and quotes the next Wednesday's release date and any cutoff time for adds. Holiday-week shifts (when new comic day moves to Thursday) come through automatically because they are in the same calendar. Customers asking 'when does the next batch arrive' get a date, not a guess.

The bot does not give a continuity lecture from training data. The configured system prompt steers it toward what is in stock or in the customer's pull list, with a quick 'this is part of the X event' or 'this is the second printing' note pulled from product description. For continuity-deep questions the bot offers to flag a staff member or links the customer to a recap site rather than inventing an event timeline.

Variants are usually separate SKUs or product variations with the cover artist tagged. SleekAI reads those. A collector asking 'do you have the J. Scott Campbell variant of this issue' gets a yes-or-no from the actual stock. For ratio variants and store exclusives, the price and quantity fields tell the bot whether a copy is still available and at what tier. Logging those queries is also where the next order quantity decision comes from.

If you offer bagging-and-boarding as a service tier on pull lists or as an add-on at checkout, the bot can describe it and link to the upgrade. The fee, the materials used (current vs Mylar), and the turnaround are all read from product or page content. Walk-in customers who want a one-time bagging job for a small collection get the price quote and the drop-off process in the same answer.

Yes. Graphic novel and manga inventory is usually WooCommerce products in their own categories. SleekAI reads them like any product. The bot can suggest the next volume of a series the customer mentioned, quote a price for a specific edition (omnibus, deluxe, single TPB), and check whether the in-print run is available. For out-of-print volumes the bot offers to flag a staff member for a backorder check.

Everything stays in the WordPress database with model name, token usage, and the page URL the chat happened on. Logged-in customers' chats are tied to their user record so the staff sees the pull-list context alongside the chat history when the customer walks in. For owners who use the logs for ordering decisions, a simple CSV export from the admin gives the weekly demand signal that drives the Diamond and Lunar orders.