Apparel Production Coordinator (Aus Fashion Brand)

Please login or register as jobseeker to apply for this job.

TYPE OF WORK

Full Time

SALARY

$245 USD/week

HOURS PER WEEK

40

DATE UPDATED

Apr 7, 2026

JOB OVERVIEW

Merchandise Administration Coordinator
Global headwear brand — Remote (must work 9am–5p ---------- lbourne / AEST Mon–Fri)
Pay: $245 USD per week (paid weekly)
Contract: Ongoing (we’re looking for someone long-term who can grow into more senior merchandising/admin responsibilities).
Start: ASAP / by mutual agreement.

Love merchandising, data and making product launches run smoothly? We’re looking for a tidy-minded merch admin who lives in PLM, gets inventory reporting, and has real-world experience in fashion/accessories/footwear. This is a hands-on, highly visible role — you’ll sit at the intersection of Product, Sales, Customer Service and Inventory and help keep the engine running.

Why this role is great
- Work with a global headwear brand and play a key role in product launches and program execution.
- Remote, but fully aligned to Melbourne hours (so you’re paid to collaborate with senior merchandisers and cross-functional teams in real time).
- Weekly pay, stable ongoing contract — ideal for merch admins who want reliable hours and a clear scope of work.

What you’ll own
- PLM data creation & maintenance — create and manage product MIDs/attributes, season/collection fields, program and custom MIDs, and ensure data architecture supports commercial reporting and forecasting.
- Order form & program setup — develop accurate order forms for launches, confirm deadlines, and ensure global MIDs are created in advance of programs.
- Inventory & sales reporting — produce weekly SOH, NOS/ATP, residual stock, sell-through and weeks-cover reporting; support wholesale and B2B reporting.
- Global range & program support — manage cancelled MIDs/program communications, post program wrap-ups, assist with global launches and forecasts.
- Cross-team collaboration — liaise with Product, Sourcing, Sales, Customer Service and Master Data teams to keep everyone aligned.
- Continuous improvement — spot data gaps, propose fixes, and improve the PLM/master data setup for smoother reporting and fewer exceptions.

What is a Product MID (short and useful)
A product MID — short for Material ID (also called Master Item ID or Style ID) — is the single, system-level identifier for a product family in your PLM/ERP.

- It’s the master record for a style or concept; individual SKUs/barcodes are created from that master.
- Typical MID fields: season, collection, product name/description, category/family, colour range, size range, composition/materials, BOM/components, cost, vendor/sourcing info, HS code/GTIN, images, and launch + sales end dates.
- Why it matters: the MID is the single source of truth for launches, costing, customs/program tracking, ordering and reporting. Clean MIDs = fewer exceptions, faster launches, and reliable inventory & sell-through reporting.

What we need from you (must-haves):
- PLM experience — essential. You’ve used PLM day-to-day (MID creation, attribute input, order form creation).
- Fashion / accessories / footwear experience — essential. You’ve worked in retail/wholesale merchandising or product admin for apparel, footwear or accessories.
- Strong Excel and data skills. Comfortable with data entry, cleanups, pivot tables and basic reporting.
- Excellent English communication. You’ll be collaborating heavily with Australia-based teams.
- Organised, accurate, and deadline-driven. You manage high volumes of product data without dropping the ball.
- Availability: Must be available 9:00am–5:00p ---------- lbourne time (AEST/AEDT) Mon–Fri.

Nice-to-haves:
- SAP experience highly regarded — not essential, but a big plus.
- Experience with BI/HANA or other reporting tools.
- Knowledge of master data best-practices and product lifecycle.
- Previous work with global program launches and sourcing teams.

What success looks like (first 3 months):
- PLM inputs for new programs and customs are timely and accurate.
- Order forms and program deadlines are consistently correct and shared on time.
- Weekly inventory and sell-through reports delivered on schedule, with clear, actionable commentary.
- Fewer data exceptions and faster program wrap-ups thanks to cleaner master data.

How to apply (please be concise)

1. When you apply, send:
- Short cover note (2–4 sentences): why you’re a fit and confirm you can work 9am–5p ---------- lbourne time.
- CV with recent merch/admin roles highlighted.
- Brief PLM summary (system name, how long you used it, and 3 core PLM tasks you owned).
- Example/report: a short description (or a redacted sample) of an inventory or sell-through report you created.

2. Screening questions (answer these in your application):
- Name the PLM system(s) you’ve used, years of experience, and the top 3 PLM tasks you owned.
- Do you have any SAP experience? If yes, describe briefly.
- Confirm you can work 9am–5p ---------- lbourne time.
- Are you comfortable with the weekly pay of $245 USD/week?

VIEW OTHER JOB POSTS FROM:
SHARE THIS POST
facebook linkedin
  BENCHMARKS  
Loading Time: Base Classes  0.0008
Controller Execution Time ( Jobseekers / Job )  0.0122
Total Execution Time  0.0135
  GET DATA  
No GET data exists
  MEMORY USAGE  
1,518,744 bytes
  POST DATA  
No POST data exists
  URI STRING  
jobseekers/job/Apparel-Production-Coordinator-Aus-Fashion-Brand-1611002
  CLASS/METHOD  
jobseekers/job
  DATABASE:  onlinejobs (Jobseekers:$db)   QUERIES: 13 (0.0072 seconds)  (Hide)
0.0003   SELECT *
                                
FROM exrates
                                WHERE rate_name 
'USD-PHP' 
0.0003   SELECT *
FROM `employer_jobs`
WHERE `job_id` = 1611002
 LIMIT 1 
0.0003   SELECT *
FROM `employers`
WHERE `employer_id` = 841419
 LIMIT 1 
0.0016   SELECT COUNT(*) AS `numrows`
FROM `t_thread` `t`
LEFT JOIN `t_thread_misc` `miscON `t`.`id` = `misc`.`thread_id`
WHERE `t`.`job_id` = 1611002
AND `misc`.`idIS NULL 
0.0004   SELECT e.business_namee.logoe.websitee.rebill_datee.date_added member_datehitsDATEDIFF('2026-04-15',ej.date_added) duration_daysDATEDIFF('2026-04-15',e.rebill_date) duration_rebillej.*, e.deactivate FROM employers eemployer_jobs ej WHERE e.employer_id ej.employer_id AND
                                   ((
e.user_level >= '500' AND ej.date_added <= e.rebill_date)
                                   OR 
e.employer_id '' OR (ej.date_approved <> '2000-01-01' and DATEDIFF('2026-04-15',ej.date_added) <= 14 ))
                                   AND 
e.deactivate != AND ej.deleted AND job_id '1611002' 
0.0003   SELECT *
FROM `employer_jobs_skills` `ejs`
LEFT JOIN `skills_categories` `scON `ejs`.`skill_id` = `sc`.`id`
WHERE `job_id` = 1611002 
0.0007   UPDATE employer_jobs SET hit_counts '***Mar-26-2026=778***Mar-27-2026=134***Mar-28-2026=30***Mar-29-2026=35***Mar-30-2026=51***Mar-31-2026=47***Apr-01-2026=710***Apr-02-2026=147***Apr-03-2026=57***Apr-04-2026=40***Apr-05-2026=40***Apr-06-2026=45***Apr-07-2026=937***Apr-08-2026=107***Apr-09-2026=34***Apr-10-2026=46***Apr-11-2026=15***Apr-14-2026=1***Apr-15-2026=1' WHERE job_id'1611002'  
0.0007   UPDATE employer_jobs SET monthly_hits '***Mar-2026=1075***Apr-2026=2178' WHERE job_id'1611002'  
0.0013   SELECT date_sent FROM jobseeker_sent_emails WHERE jobseeker_id '' AND job_id '1611002' AND status LIKE 'sent%' ORDER BY id DESC  
0.0003   SELECT *
FROM `employer_jobs_skills` `ejs`
LEFT JOIN `skills_categories` `scON `ejs`.`skill_id` = `sc`.`id`
WHERE `job_id` = 1611002 
0.0004   SELECT COUNT(*) AS `numrows`
FROM `employer_jobs`
WHERE `employer_id` = '841419'
AND `date_added` >= '2022-06-08' 
0.0002   select from teasers 
0.0002   SELECT FROM skill_categories WHERE skill_cat_id='' 
  HTTP HEADERS  (Show)
  SESSION DATA  (Show)
  CONFIG VARIABLES  (Show)