Shipping and Fulfillment Setup

Documentation Index

Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt

Use this file to discover all available pages before exploring further.

​

Open the Shipping and Fulfillment Settings

1. Open Settings.
2. Choose Entity Settings.
3. Open the Shipping and Fulfillment group for Shipping, Shipping Rules, Packing Configuration, and Scanners.
4. Open the System group for Printing.

​

Shipping Settings

The Shipping section controls the default carrier behavior Arcus uses when a user packs an order or buys a label. It also checks whether the Shippo connector is active for the current entity.

• Shippo Connection: shows whether the entity has an active Shippo connector and lets admins test the connection.
• Default Carrier and Service: used when no shipping rule matches the package.
• Label Format: choose PDF, PNG, or ZPL for thermal printer workflows.
• Default Package Type: preselects common package types when package data is incomplete.
• Signature and insurance thresholds: tell the packing workflow when higher-value shipments need extra services.
• Residential surcharge handling: pass through, absorb, or add a flat fee when a residential label is purchased.

​

Rate Automation

Rate automation controls how much Arcus does automatically after packages are created. Use the most automated settings only after the team has tested package dimensions, addresses, label format, and printer routing.

• Auto-fetch rates when package is created: asks Shippo for rates as soon as a package exists.
• Auto-select cheapest rate: chooses the lowest-cost available rate instead of asking the user to choose.
• Auto-fetch rates on pack: runs rate shopping after PackPilot creates package cards.
• Auto-buy label on pack: buys the label after rates are fetched, using preferred rule settings first and the cheapest rate as fallback.
• When no rates are available: show a warning or use the flat rate from shipping rules.

​

Shipping Rules

The Shipping Rules section controls carrier routing. Rules can match by location, weight, order value, sales channel, product category, and carrier service token. Lower priority numbers are evaluated first.

• Apply to: choose all locations or a specific warehouse. Location-specific rules are evaluated before entity-wide rules.
• Weight and order value: use ranges to separate small parcel, heavy parcel, and large-order behavior.
• Sales channel: route Shopify, marketplace, phone, counter, or other channel orders differently.
• Product category: apply special shipping policy to categories that require different carriers or service levels.
• Carrier tokens: limit which Shippo service tokens are allowed for the rule.
• Preferred carrier and service: guides auto-label purchasing when automation is enabled.
• Free shipping and flat rate: controls what the customer is charged. It does not change the carrier cost Arcus pays.

​

Freight Classification Rules

The bottom of Shipping Rules includes freight classification rules. These rules decide whether an order should stay parcel, move to LTL freight, suggest freight review, add accessorials, or block the order.

• Freight rules are also priority-based. The first matching rule can change the shipping mode.
• Rules can look at weight, dimensions, product freight flags, customer preferences, and similar freight signals.
• If Shippo freight rate shopping is unavailable for the account, users can still enter freight quotes manually.
• Manual freight overrides are respected until a user removes or changes the override.

​

Packing Configuration

Packing Configuration controls PackPilot behavior and packing algorithm scoring. It also includes packing presets used by the algorithm to decide which carton layout is best.

• Auto-suggest PackPilot cartons: creates suggested packages when an order reaches ready-to-pack. Packers can accept or discard the suggestion.
• Default new cycle counts to Blind mode: sets the default counting mode for new cycle counts. It affects inventory counting, not label buying.
• Base per box and per pound: influence the algorithm’s cost score when comparing carton layouts.
• Oversize penalty and limit: discourage packages with dimensions above the configured limit.
• DIM weight factor: controls dimensional-weight scoring. Carrier rates may still apply their own divisor through Shippo.
• Epsilon: tolerance used in floating-point comparisons when evaluating fits.
• Packing presets: saved parameter sets that can be created, edited, tested, and marked default.

​

Scanners

The Scanners section manages Zebra and Arcus Command devices. Devices register automatically after a warehouse user connects the app to the entity and signs in with their PIN.

• New Device Setup: shows the entity setup code and QR code for Arcus Command.
• Registered Devices: shows each scanner, assigned user, assigned location, last seen time, and sync status.
• Sync toggle: turns scanner sync on or off without deleting the device assignment.
• Device details: shows the scanner ID and DataWedge configuration when setup troubleshooting is needed.
• Recent Scans: filters by date, device, type, and barcode text.

​

How Barcode Scans Are Classified

The backend is the source of truth for scan type. The frontend receives the classification and reacts to it. This keeps scanners consistent across packing, serial capture, and logs.

• Serial: package-scoped serial format or a matching serial number.
• Label: tracking number or shipment label match.
• Box: product barcode that belongs to a box product.
• Item: product barcode for a non-box product.
• Order: order number match.
• Unknown: no match found. The scan still lands in the log for review.

​

Printing

The Printing page sets per-user PrintNode preferences for the current entity. It uses the entity’s PrintNode connector, then lets each user choose default printers and auto-print behavior.

• PrintNode connection: depends on the PrintNode connector in Integrations.
• Default label printer: used for shipping labels, usually a thermal 4x6 label printer.
• Default document printer: used for packing slips, invoices, pick lists, and letter-size documents.
• Auto-print on fulfill: sends label and packing slip jobs automatically when a package is fulfilled.
• Printer category filters: limit fulfillment station package visibility by product packing category when a filtered printer is selected.
• Recent Print Jobs: shows submitted, failed, queued, and offline-blocked jobs with filters.

​

Recommended Setup Order

1. Configure locations first, including the ship-from address.
2. Connect Shippo and test the connection.
3. Set label format and default carrier fallback.
4. Add shipping rules for common parcel lanes.
5. Add freight rules for orders that should not ship parcel.
6. Review product dimensions, weights, box products, and packing categories.
7. Configure PackPilot suggestions and packing presets.
8. Connect PrintNode, install the PrintNode client, and select user printer preferences.
9. Register warehouse scanners through Arcus Command and verify recent scan logs.
10. Run a test order through pick, pack, rate, label, print, and fulfill.

​

Common Blocks

• No rates returned: check Shippo connection, ship-from address, ship-to address, package dimensions, weight, and allowed carrier tokens.
• Wrong carrier selected: review rule priority, preferred carrier, preferred service token, and auto-select settings.
• Flat rate charged but carrier cost differs: this is expected. Flat rate is customer charge policy, not carrier cost.
• Auto-buy did not run: check auto-fetch on pack, auto-buy on pack, rule preference, Shippo connection, address validation, and label format.
• PackPilot suggestions are missing: check the auto-suggest toggle, product dimensions, stock, serial requirements, freight mode, bins, and Audit Log.
• Scanner is offline: confirm the Arcus Command app is open, sync is on, the device has network access, and the user is signed in with PIN.
• Barcode scans as unknown: verify the barcode belongs to an order, product, serial number, box product, label, or supported package-scoped serial format.
• Print jobs do not print: check PrintNode connector, PrintNode client status, printer online state, user printer preferences, and recent print job errors.
• Printer only shows some packages: review printer category filters. A filtered printer only shows packages containing matching product categories.

​

Related Articles