What syncs between Katana and Pod Foods
The table below summarizes each data flow between Katana and Pod Foods.
Data | Direction | Status |
Products | Pod Foods → Katana | Available |
Inbound stock transfers | Pod Foods → Katana | Available |
Inventory sync | Pod Foods → Katana | Available |
Locations and mapping
After Pod Foods approves the connection, the configuration screen opens on the Location tab. Each Pod Foods warehouse maps 1:1 to its own dedicated Katana location.
Add to Katana creates a new Katana location for a warehouse. Until then, the warehouse shows as Not mapped.
Unlink pauses a mapped warehouse, and its status shows Unlinked.
Relink resumes syncing for an unlinked warehouse.
Only mapped warehouses sync.
Products sync
Product mapping is required. It links each Pod Foods product to a Katana item by SKU. You can match SKUs in one of two ways:
Direct 1:1: each Pod Foods SKU matches the identical Katana SKU.
Via SKU aliases: each Pod Foods SKU matches a different Katana SKU.
During product import, a Pod Foods SKU that already exists in Katana links to that product. Katana creates a new product just in time for any SKU it doesn't recognize.
Kits and bundles from Pod Foods also become Katana products. To track their components, add a bill of materials (BOM) to the kit in Katana.
SKU aliasing
A SKU alias connects a Pod Foods SKU to a different Katana SKU. Use aliases when the same product has a different SKU in each system. For example, Pod Foods might use a case-pack SKU while Katana uses your internal item code.
Upload your SKU alias mapping before you import products. Otherwise, the mismatched SKUs create duplicate products.
Inventory sync
Pod Foods stock levels appear in Katana as read-only External inventory. You can see them at the Katana location mapped to each warehouse, and On hand is the number shown. Pod Foods publishes inventory files daily, so the figures reflect its latest file.
Reconciliation compares Katana's in-stock quantity with the Pod Foods on-hand quantity only. Reconciliation runs on a schedule or on demand. When the two numbers differ, Katana creates a stock adjustment for the difference, so your stock levels match Pod Foods.
Inbound shipments
Each Pod Foods inbound shipment becomes one Katana stock transfer. The transfer number is the PO number when the shipment has one. Otherwise, it's the inbound ID.
Destination: the Katana location mapped to the inbound shipment's warehouse.
Origin: the location you assign for each destination warehouse. You must map an origin location.
Each stock transfer follows the status of its inbound shipment. When Pod Foods receives items, Katana updates the received quantities on the transfer. If an inbound shipment is canceled, Katana deletes its stock transfer.
Katana stock transfers have two states: in transit and received. During partial receiving, the transfer's expected and received quantities update until the shipment is fully received.
What does not sync
Sales orders. Pod Foods orders don't import into Katana, and Katana doesn't send orders to Pod Foods.
Fulfillments and tracking information.
Products or stock changes from Katana. Katana never sends these to Pod Foods.
Returns and RMAs.
Serial-number tracking. Katana shows lot and batch data as read-only where Pod Foods provides it.
Disconnecting
Go to Katana's Integrations page, open the Pod Foods integration, and disconnect it. Syncing of inventory, inbound shipments, and products stops right away.
Records Katana already imported stay in Katana, including products, locations, stock transfers, and stock adjustments.