MCO Inventory: Push a Shared SKU to Multiple Clubs (Centralized SKU)

When You'll Use This

• Setting up new merchandise at HQ that needs to roll out to multiple satellite clubs

• Launching a new branded apparel line, F&B item, or pro shop product across the group

• Standardizing inventory taxonomy across clubs (so the same items show up the same way everywhere)

If you've been doing 10 separate SKU creates for one shared item, this is the workflow you've been waiting for.

Step 1: Enable Centralized SKU for Each Participating Club

Verify before publishing: the exact admin path. Brendan O'Brien's unanswered April 28 question is exactly this. The KB will be updated with the confirmed steps once Michael Rawlins responds.

In the MCO Portal, locate the new Has Common SKUs column. By default, every club is set to No.

For each club that should participate in Central Inventory (both as a possible source and as a recipient), toggle the column to Yes.

Note: The feature is per-club — clubs with the column set to No won't appear in the push checkbox list, and items at those clubs can't be pushed to other clubs.

Step 2: Create the SKU at the HQ Club

At the HQ club, create or open the inventory item exactly as you normally would. Set the:

• Department

• Sub-department

• Category

• Inventory Type and Sub Type

• Item Name

• Stock amount

• Barcode

• SKU

• Item Cost, Sale Price

• Loyalty Redemption, Loyalty Earned, Loyalty Earned Type

• Floor Price

• Tax Group (sales tax or no sales tax)

• Vendor

These are all the fields that get carried to each receiving club when you push.

Step 3: Push the SKU to Selected Clubs

At the bottom right of the inventory item, you'll see a new button that opens a per-club checkbox list for distribution.

Check the boxes for the clubs that should receive this SKU. Click Submit.

The system creates the inventory item at each selected club, with the configuration set up automatically.

Note: If a receiving club's Department / Sub-department / Category structure doesn't match the HQ club's exactly, the system will skip that club and show you a popup listing which clubs were skipped and why. From there you can either fix the receiving club's structure or accept the partial push.

What Receiving Clubs Can Edit (and What They Can't)

Once the SKU is pushed, the receiving club has its own copy of the item. The receiving club's staff can edit every field on the cloned item — except:

• Barcode — locked

• SKU — locked

This is intentional. Locking these two fields prevents accidental drift across the group, so the same SKU and barcode mean the same item at every club.

Everything else — stock amount, sale price, vendor, loyalty settings, even the item name — is editable at the receiving club.

What Happens if Department Structures Don't Match

The push relies on Department / Sub-department / Category being identical at HQ and at the receiving club. If a receiving club's structure differs in any of those three places, the push skips that club.

When that happens, a popup appears showing:

• Which clubs were skipped

• The mismatched structure that caused the skip

You then have two options:

1. Fix the receiving club's structure to match HQ, then re-push

2. Accept the partial push — the SKU goes to the clubs that matched, and the skipped clubs can have the item created manually if needed

Watch Out For

• No general Settings toggle. Don't look for "Central Inventory" in your standard Settings menu — the toggle lives in the MCO Portal at the club level.

• Pushing without checking structure first. If receiving club categories don't match HQ, the push will skip them and you'll have rework. Verify Department / Sub-department / Category structure across clubs before doing a bulk push.

• Locked Barcode and SKU at receiving clubs. Staff at a receiving club can't change these. If they try, they'll hit a wall — let them know in advance.

• One-way push. This is HQ → satellites. Changes made at a satellite don't flow back to HQ or to other satellites.