Platform

Move operational data without the spreadsheet cleanup project

Choose the records that should leave Cybership, keep each file shaped for its resource, and bring valid changes back without losing the exact rows that need correction.

Choose the rows first; let that decision shape the file

Two checked inventory rows in the filtered DAL-01 view make Selected rows the default scope. This page, Search & filters, and All results remain available when the operator needs a broader handoff.

The resulting Inventory CSV carries sku, action, quantity, location, and warehouse_name. Current on-hand values leave with Replace intent, so the downloaded file is an explicit starting point instead of an unlabeled quantity dump.

Inventory

2 rows selected from the current filtered view

Warehouse · DAL-01
Location type · Pick face
  • Rugged Camp Mug

    RUGGED-MUG-12

    18
    A-01-01DAL-01
  • Field Repair Kit

    FIELD-KIT-02

    7
    A-01-02DAL-01
  • Trail Light

    TRAIL-LIGHT-04

    31
    B-02-01DAL-01
  • Camp Utility Strap

    CAMP-STRAP-08

    12
    B-02-02DAL-01

Export inventory

Choose the record scope

2 selected
  • Selected scope: Selected rows

    Only records checked in the current table.

  • This page

    Every record visible on the current page.

  • Search & filters

    All records matching the active query and filters.

  • All results

    The full resource set for the current team context.

The current selection wins before page, query, or full-resource scope.

Selected rows become the file

The two checked DAL-01 inventory rows produce an Inventory CSV with the resource's supported columns and Replace already attached to each current on-hand value.

Inventory export

Selected rows · 2 records · CSV

Completed
  • Row 1

    RUGGED-MUG-12

    Replace
    Quantity
    18
    Location
    A-01-01
  • Row 2

    FIELD-KIT-02

    Replace
    Quantity
    7
    Location
    A-01-02
Inventory exports start each row with Replace so the file describes the current on-hand state explicitly.

What travels with each row

The Inventory CSV fields operators can review

sku
Identifies the product in the current team’s catalog.
action
Replace by default; Change is also accepted on import.
quantity
A signed integer for Change or the final count for Replace.
location
Resolves a location name inside the current team’s warehouse set.
warehouse_name
Keeps warehouse context visible in the exported review file.

Say whether each quantity is a change or the final truth

Rugged Camp Mug uses Replace to move from 18 on hand to a final count of 24. Field Repair Kit uses Change -2 to move from 7 to 5. The action travels with the row instead of living in someone's memory.

Replace computes the difference needed to reach the entered final quantity. Change applies a signed delta. Non-integer quantities and unsupported actions are rejected before inventory changes.

Inventory adjustment.csv

2 intended changes and 2 rows that need correction

4 data rows
  • Row 1

    RUGGED-MUG-12

    Replace
    Quantity
    24
    Location
    A-01-01
  • Row 2

    FIELD-KIT-02

    Change
    Quantity
    -2
    Location
    A-01-02
  • Row 3

    TRAIL-LIGHT-04

    Replace
    Quantity
    2.5
    Location
    A-01-03
  • Row 4

    CAMP-STRAP-08

    Set
    Quantity
    12
    Location
    B-02-02

Replace means final state

18 → 24

Cybership computes the difference from current on-hand and sets the location to the entered quantity.

Change means signed delta

7 + (-2) = 5

Cybership increments or decrements the current stock by the signed quantity in the row.

The CSV keeps intent in the row; operators do not have to infer whether a number is a target or a delta.

Keep the accepted rows; repair only what was rejected

The Inventory Upload completes with 4 Processed Items and 2 Failed Items. Job Logs keeps the standard All, Errors, and Success views with Row and Message, so the two invalid source rows stay specific.

Rows 1 and 2 remain applied. Correct the non-integer quantity on row 3 and replace Set on row 4, then start a new Inventory Upload job so accepted changes are not silently replayed.

Inventory Upload

Completed with row errors

Completed
Processed Items
4
Failed Items
2

2 of 4 rows failed

Invalid rows do not change inventory. Valid rows remain applied.

Job Logs

All
Errors
Success
  • Row 1

    Replace 24 at A-01-01

  • Row 2

    Change -2 at A-01-02

  • Row 3

    Parse error: Invalid input: expected int, received number

  • Row 4

    Parse error: The 'action' column must be either 'Change' or 'Replace'

Keep the accepted work

Rows 1 and 2 have already applied. The correction path starts from rows 3 and 4 instead of asking the team to replay all four.

Repair only the rejected source rows

Accepted changes stay put; corrections start a new import

  1. 01

    Keep the accepted rows

    The accepted Replace and Change updates remain attached to the completed import job.

  2. 02

    Correct only rows 3 and 4

    Use the row-numbered messages to enter a whole-number quantity and replace Set with an accepted action.

  3. 03

    Start a clean follow-up import

    Submit the corrected source rows as a new job instead of silently replaying committed work.

Completed export

Download Export · 30 days

Correction

Starts a new Inventory Upload job

Use the right file contract for the resource

Each table exposes the file workflow it can safely support. Resources marked Import accept writes; review and reconciliation surfaces remain export-only.

CSV output
Resource permissions
Team scoped

Products

Import supportedExport supported

Create or update supported fields; barcode and inventory export columns stay read-only.

Inventory

Import supportedExport supported

Edit-ready stock rows with Change or Replace quantity intent.

Locations

Import supportedExport supported

Resolve warehouse and location type, then create or update by warehouse and name.

Totes

Import supportedExport supported

Create or update by warehouse and name, with optional barcode generation.

Cartons

Import supportedExport supported

ID and _lock make unchanged re-import rows skippable.

Location types

Import supportedExport supported

ID and _lock make unchanged re-import rows skippable.

Orders

Import not supportedExport supported

Operational review and external reconciliation export.

Fulfillments

Import not supportedExport supported

Fulfillment, shipment, service, warehouse, and line-item detail.

Shipping labels

Import not supportedExport supported

Tracking, carrier, service, price, status, destination, and dates.

Purchase-order line items

Import supportedExport supported

One purchase order at a time, using the same line-item columns in both directions.

Report chart data

Import not supportedExport supported

Export the underlying chart data as CSV from a report run.

Team members

Import supportedExport not supported

Template-led import with role, warehouse, hierarchy, and seat-limit checks.

Keep scope, quantity intent, and rejected rows visible at every file boundary

The gain is control at each boundary: choose the records, keep quantity intent in the CSV, reject malformed rows by number, preserve valid work, and keep the result attached to a team-owned job.

Export scopes
4Selected rows, current page, active search and filters, or the full team-owned resource set.
Import and upload types
8Active CSV job types across operational resources, scoped purchase orders, and team members.
Export types
11Active resource and report-data job types that produce CSV output.
Export retention
30 daysGenerated CSV files remain available for download for the full retention window.

Trusted by 3PLs and brands

2FLYcoAmmoSquaredAxion FulfillmentIndustry Thread Worksadrafül labs

See it in your operation

Bring us the spreadsheet your team is afraid to import

Show us the product update, inventory correction, location rollout, purchase-order cleanup, or reconciliation export that still needs manual cleanup. We’ll map its scope, file shape, quantity intent, row validation, and repair path against your operation.

No sales call is required to get sandbox access.

Continue exploring

View all features