November 13, 2026

Viktor for Amazon Sellers: Seller, Vendor and Ads Reporting in Slack

How to connect Viktor, the AI employee in Slack and Teams, to Amazon through DataDoe, what to schedule, and how approvals keep changes under control.

Most Amazon teams already talk about Amazon in Slack or Microsoft Teams. Someone pastes a screenshot from Seller Central, someone else asks whether it includes Vendor, a third person opens the ads console to check spend, and by lunchtime the thread has five numbers that do not agree. Viktor is built for exactly that kind of thread: instead of a person fetching the numbers, an AI colleague does it and posts the answer where the question was asked.

This guide covers what Viktor is, what DataDoe gives it, how to connect the two, which requests are worth putting on a schedule, and how to keep control of anything that would change your account.

What Viktor is

Viktor is an AI employee made by Zeta AI. A company adds it once to its Slack or Microsoft Teams workspace (Discord and a web app work too), and anyone on the team can mention @Viktor in a channel or a direct message. Behind the chat, Viktor has its own cloud computer where it writes and runs code, so a request can end as a PDF, a spreadsheet, a chart or a small internal app rather than a paragraph of text.

Three things make it different from a chatbot in a sidebar:

  • It is shared. One Viktor serves the whole workspace, and the price is not per seat. What it learns in one channel is available to the team.
  • It keeps routines. When a result is right, you can ask Viktor to save it as a skill and run it on a schedule.
  • It works through connected tools. Viktor lists more than 9,800 integrations, and any remote MCP server can be added as a custom one.

What DataDoe gives Viktor

DataDoe and Viktor work together, and DataDoe is in Viktor's integration catalogue. Once it is connected, Viktor works from the whole Amazon business rather than one report at a time:

  • Seller Central, Vendor Central and Amazon Ads in one schema, so a single answer can cover all three.
  • Every Amazon marketplace you sell in and every account in your organization.
  • Ad spend and sales in the same answer, matched by SKU and ASIN.
  • Profit, with your product costs next to Amazon's fees and the ad spend.
  • History stored every day, so "against last year" is a real comparison.

The rest of the picture, with examples, is on our Viktor integration page.

Connecting DataDoe to Viktor

  1. Link Amazon to DataDoe. Authorize Seller Central, Vendor Central and Amazon Ads on Amazon's own consent pages. If you care about profit, upload your product costs now; it is the step most people skip and then wonder why "profit" equals revenue minus fees.
  2. Add DataDoe in Viktor. Open Integrations and pick DataDoe from the catalogue.
  3. Sign in. Viktor opens the DataDoe sign-in in your browser and stores the connection.
  4. Name it and decide who uses it. Give the connection a clear nickname, for example "DataDoe, all brands". In a Slack or Teams workspace, set access to everyone or to invite-only.
  5. Set tool levels. Each tool can run automatically, ask for confirmation, or be off. Reading can run on its own; anything that changes Amazon should ask.

Then go to the channel where Amazon is discussed and ask a first question. Something you already know the answer to is ideal, because it tells you straight away whether the numbers line up with what you see in Seller Central.

How to write a request Viktor gets right the first time

Viktor will answer a vague question, but a precise one becomes a routine you can trust. Four details matter more than anything else:

  • Which accounts. "US and DE Seller, plus Vendor US" removes the guesswork when the organization holds several.
  • What profit means. Say "after Amazon fees, ad spend and product costs" so the definition is written into the request, and later into the skill.
  • One currency per table. A total that adds dollars and euros is noise. Ask for one table per currency, or a conversion at a rate you name.
  • The comparison. "Against the same weekday last year" or "against the previous four weeks" is more useful than a raw number.

Once the first answer is right, ask Viktor to save it as a skill with those definitions. That is what turns a lucky answer into one that arrives the same way every Monday.

Six requests worth putting on a schedule

Daily sales pulse

"Each morning at 7:30, post yesterday's orders and sales per marketplace against the same weekday last year. Mark anything more than 20% off in either direction." Short, comparable and quick to read on a phone.

Search terms that cost money and sold nothing

"Every Friday, list Sponsored Products search terms with more than $30 spend and no orders in the last 14 days, grouped by campaign." This is a review list, not an automatic negation; a person decides.

Featured Offer losses

"Twice a day, check our top 30 ASINs for a lost Featured Offer and say how far below us the winning offer is." Pair it with a pricing rule later, once the alerts look trustworthy.

Payout check

"After each settlement, show what Amazon paid, what it deducted and anything that differs from the previous settlement by more than 10%." Finance teams like this one in their own channel.

Month-end profit pack

"On the first working day of each month, build last month's profit by brand and marketplace as a PDF, with the definitions on the last page." The definitions page saves an argument every month.

New Vendor purchase orders

"Every weekday, summarise new Vendor Central purchase orders and compare the quantities with the last four weeks." It catches the quiet drop in ordering that otherwise shows up weeks later in revenue.

Keeping control of changes

Viktor and DataDoe each have a lock, and a change on Amazon needs both to be open.

  • In Viktor, the tool level decides whether Viktor may use a tool without asking. "Ask for confirmation" posts an approval in the thread, and someone has to press approve.
  • In DataDoe, each kind of change (prices, listings, ads, orders) is an Action type that stays off until you switch it on, each Amazon account is read only or read and write, and every Action can be run as a dry run first. Every Action that runs is logged with what was sent.

A sensible start is read only for the first week. Then switch on one Action type, usually ad bids, keep Viktor on ask for confirmation, and widen it only when the approvals have been boring for a while.

For agencies

An agency can add one DataDoe connection per client, name each one after the client, set them to invite-only, and tell Viktor which connection a client channel uses. Clients connect their own Amazon accounts through a DataDoe invitation link, so nobody at the agency handles their logins, and each account can be read only or read and write. The rest of the agency setup is on our agencies page.

Mistakes we see

  • One connection for every channel. If every channel can see every client, sooner or later a brief lands in the wrong room.
  • Profit without costs. Without product costs uploaded, the number is a margin before cost of goods, whatever the request calls it.
  • Reading the last two days of traffic as final. Sessions and conversion arrive later than orders and move for a few days. Compare complete weeks.
  • Running changes automatically on day one. Let the approvals prove themselves first.

Where else this works

If your team prefers Claude inside Slack, the same DataDoe connection works there; see Claude in Slack for Amazon. If you run the business mostly from your phone, Boski does the same by text message. Vendor-specific data is described on our Vendor Central page.

Questions people ask

Does Viktor need my Amazon login?

No. You authorize Amazon in DataDoe on Amazon's own pages, and Viktor signs in to DataDoe.

Can people outside the Amazon team ask about Amazon?

Only if the connection's access allows it. Set it to invite-only to keep it to the people who should see the numbers.

Does it work in Microsoft Teams?

Yes. The connection belongs to Viktor, so it works wherever Viktor does: Slack, Microsoft Teams, Discord and the web app.

How fresh is the data?

DataDoe fetches most tables daily at 2:00 in the seller's local time, with some tables updated during the day. Viktor reads whatever DataDoe holds at the moment of the request.

What does it cost?

DataDoe is $97 a month after a 14-day free trial, with every Amazon account included. Viktor is billed separately in credits shared across the workspace and starts free.

Viktor is a product of Zeta AI, Inc., and a DataDoe partner. DataDoe has no affiliation with Amazon and is not endorsed by Amazon. The Viktor steps follow Viktor's documentation as read on 12 November 2026 and may change.

• Get started

Put this to work on your own Amazon data.

Connect Seller Central, Vendor Central and Amazon Ads in about 5 minutes, then ask your AI about your own numbers instead of the examples in this post.

  • Seller, Vendor and Ads
  • Any AI client
  • An account manager for every customer
  • $97/mo, 14-day free trial