GoatLabels GoatLabels

Security Review Questions for Shipping Software

The security questions to send a shipping software vendor, grouped by data, access, API keys, payments, logging and incidents, and how to read the answers.

Get free rate quotes Free account. No card needed.

A security review of shipping software should ask what data the vendor holds, who and what can reach it, how API keys and card payments are handled, what gets logged, and what happens when something goes wrong. Send the same short list to every vendor, ask for evidence behind each answer, and decide in advance which answers are must-haves. The general buying questions on carriers, billing and contract terms are in 20 questions to put in a shipping software RFP; this post covers the security half only.

Which questionnaire should you send a shipping software vendor?

Send a short custom list or a lite standard questionnaire, not a full enterprise assessment, unless the vendor will hold data your policy rates as critical. Two standard formats come up most often.

The SIG (Standardized Information Gathering) questionnaire, per Shared Assessments, "standardizes the initial assessment of vendors and other third parties" and is updated at least annually. Shared Assessments says the 2023 SIG Lite has 126 questions for basic due diligence on initial or less critical vendors, while the 2023 SIG Core has 855 questions for a comprehensive assessment.

The Cloud Security Alliance's STAR Level 1 Security Questionnaire (CAIQ v4.1), released January 27, 2026, "provides a set of Yes/No questions a cloud consumer and cloud auditor may wish to ask of a cloud provider" to check it against the Cloud Controls Matrix. CSA also publishes a CAIQ-Lite with 138 questions across 17 control domains.

For most parcel shipping tools, a SIG Lite, a CAIQ-Lite, or the 20 questions below is the right size. If a vendor sends a completed form instead, map its answers to your list. For the wider set of buying guides, start at the B2B shipping software hub.

What does a SOC 2 report tell you, and what does it not?

A SOC 2 report tells you what a CPA firm found when it examined the vendor's controls; it does not tell you those controls fit your use. The AICPA describes SOC as "a suite of service offerings CPAs may provide in connection with system-level controls of a service organization," and its SOC 2 guide covers controls relevant to security, availability, processing integrity, confidentiality, or privacy.

Three details decide how much weight a report carries:

  1. Type. According to Wolters Kluwer, "a Type 1 report is as of a specified date (single point in time), whereas a Type 2 report is throughout a specified period (usually a 6-12 month period)." A Type 2 is closer to what you need.
  2. Scope. The same source says SOC 2 covers security and, optionally, availability, confidentiality, privacy and processing integrity. Check which criteria and which systems are in scope. A report on a billing system says nothing about a label API.
  3. Exceptions and dates. Read the auditor's opinion and any exceptions, and note when the period ended. An old period describes a system that may have changed.

Wolters Kluwer also notes that SOC 1 and SOC 2 reports have restricted distribution, while a SOC 3 is a general-use report, always Type 2, without the detailed tests and results. A SOC 3 on a website is a summary, not a substitute.

Watch the wording. SOC 2 is an examination and a report, not a certificate, so "SOC 2 certified" is a cue to ask for the report itself. As of October 21, 2026, the AICPA's SOC page carried a notice that it is looking into allegations about a SOC compliance vendor, and said "SOC services should be thoroughly evaluated by service organizations and CPA firms." Note which CPA firm signed the report.

Which questions should you ask in each domain?

Ask questions that force a specific answer, then ask for the evidence. A yes with no document, screenshot or report section behind it counts as a partial.

Data

  1. Which of our data do you store: ship-to names, addresses, phone numbers, emails, item descriptions, declared values, order references?
  2. Where is it hosted, and which subprocessors (hosting, email, payments, carriers) receive it?
  3. Is data encrypted in transit and at rest? Which data, and how?
  4. How long do you keep shipment and address data, and can we have it deleted when we leave?

Access

  1. How do our people sign in, and is single sign-on (SAML) supported?
  2. Are there roles, so we can separate who buys labels from who only views?
  3. How is your own staff's access to customer data granted, reviewed and removed?

API keys and webhooks

  1. Are keys shown once and stored only as a hash, or can your staff retrieve them?
  2. Can we create read-only keys, and keep test keys separate from live keys?
  3. Can we rotate or revoke a key ourselves, and does the old secret stop working right away?
  4. Can we see when each key was last used?
  5. Are webhooks signed, and with what algorithm, so we can reject forged calls?

Question 12 matters when webhooks write into your systems, as in sending tracking back to your ERP with webhooks.

Payments

  1. Do you store, process or transmit card numbers, or does a card processor handle them?
  2. How do you validate PCI DSS compliance, and how do you monitor your processor?

Logging

  1. Is there an audit log of who did what in our account: purchases, voids, key changes, setting changes?
  2. Which logs can we see ourselves, and how long are they kept?
  3. Are API requests and webhook deliveries logged, and can failed deliveries be replayed?

Incident response

  1. How and how fast will you notify us of an incident that affects our data, and who is the contact?
  2. When did you last test your incident response plan?
  3. When did you last restore production data from a backup?

Questions 5, 6 and 15 are where smaller shipping tools differ most from enterprise platforms. If any of them is a must-have, the enterprise shipping software guide explains which kinds of platform fit that checklist.

How does PCI DSS apply when a vendor outsources card payments?

It still applies, and the vendor should be able to say how it checks its processor. Per the PCI Security Standards Council, PCI DSS still applies to merchants that outsource all payment processing. Many requirements may not apply directly. The merchant must still make sure the provider is compliant, keep written agreements (Requirement 12.8.2), monitor the provider's compliance at least annually (Requirement 12.8.4), and validate, typically with a Self-Assessment Questionnaire such as SAQ A.

So a good answer to question 14 names the vendor's validation path and how it monitors the processor. "Our processor handles PCI" is a partial answer.

Check your own side too. A label needs addresses, weights and references, not payment details, so the order exports and API payloads you send should carry no card data.

How do you read the answers?

Read each answer for what it proves, not how confident it sounds. Score each one as yes with evidence, partial, or no, and treat a no on a must-have as a stop regardless of the rest.

Question Vendor answer (example) Reading Follow-up
SOC 2 "We are SOC 2 certified." Wrong word, no report seen Ask for the report, its Type and period end date
3. Encryption "All data is encrypted." Too broad Ask which data, in transit and at rest
8. Key storage "Shown once, stored hashed." Yes, if a trial matches Create a key and confirm it cannot be viewed again
10. Rotation "Rotation supported." Partial Ask whether the old secret stops at once
14. PCI "Our processor handles PCI." Partial Ask for the validation type and how the processor is monitored
15. Audit log "On the roadmap." No Decide whether it is a must-have

Example: a reviewer scores one fictional vendor's 20 answers as 12 yes with evidence, 5 partial and 3 no. Two of the no answers, SSO and the audit log, are on the company's must-have list, so the vendor fails. If neither were a must-have, the 5 partials would become written follow-ups due by Friday, December 18, 2026.

Verify what you can yourself. Key handling, read-only scopes, last-used dates and webhook signatures can be checked in a trial account. Policy answers, such as incident notice, need documents.

Where GoatLabels fits

GoatLabels answers the API key and webhook questions with details you can check in a trial. On the v1 API, the account owner creates keys on the dashboard Developers page. Each key is live or test and full access or read-only, and a read-only key gets a 403 on a write. The full key is shown once, and only a SHA-256 hash is stored. Keys can be rotated (the old secret stops working immediately), revoked or deleted, and the keys table shows scopes, mode and last-used date. Webhooks are signed with HMAC-SHA256, and each endpoint has its own secret and must use https. Card numbers are not stored by GoatLabels; its card processor handles them. Data in transit uses TLS. The shipping API for developers page has the details.

The limits matter here. GoatLabels has no SSO and no audit log, so questions 5 and 15 are a no. The company does not claim SOC 2 or ISO 27001. If any of those are must-haves, it will not pass your review. Send the rest of your questionnaire to contact@goatlabels.io.