Skip to content
Hypamoon

For teams that run on Quivo

Quivo inbound: see what arrived short

When the warehouse counts something else than you announced, the inbound stays on processing and the difference sits at the bottom of the inbound page, with photos and comments. Quivo asks you to check with the carrier and the supplier first, before you open a case.

How it goes today

  1. Open each inbound that stays on processing.
  2. Scroll to the table with planned, received and difference.
  3. Save the photos and comments from the warehouse.
  4. Write the supplier about the short units and Quivo about the rest.

How it can go

After each Quivo inbound you know what arrived short or over, per SKU, and what to ask your supplier.

When an inbound is received, you get the differences per SKU: announced, received and the gap, with the photos and comments from the warehouse and the delivery slip number. Per supplier there is a short draft email about the units that did not arrive, which you send yourself. Inbounds that have not arrived a few days after the expected date are listed too.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. You paste your Quivo key in the portal, never in the chat.

Your request

With Hypamoon, when Quivo receives one of our inbounds, show me per SKU what we announced, what arrived and the difference, with the photos and comments from the warehouse and the delivery slip number. Draft a short email per supplier about the units that did not arrive, for me to send. Also list inbounds that have not arrived a few days after the expected date.

An account admin creates the API credential, a client ID and secret, in the Quivo Connector under Admin, API Credentials. No approval from Quivo is needed. The API comes with the Stellar Explorer plan and up. It stays yours.