본문으로 건너뛰기
Workshop overview
Chapter 3 of 7
15 min

Enrich inventory with the competitor price

Run the price-update pipeline and interpret one before-and-after row and the complete output scope.

Question for this chapter

What does the pipeline change in an inventory row, and what does it preserve?

Why this matters now

The dashboard reads price-adjustment candidates from the enriched output. Without verifying the run, an old competitor price could be mistaken for a current observation.

Try it

Open Competitor Price Update under Pipelines and inspect the four connected nodes.

Pipeline connecting Product Information and Competitor Price Data to an output dataset
Verify the two inputs, price-update code, and output dataset.

Select the code node. It left-joins the two inputs on item_code and changes only competitor_price_krw_synth where an observation exists.

Configuration panel for the competitor-price update code node
Verify that the code node receives two inputs and creates the output.

Select Run now in the upper-right. When the run completes, open Data and Version history in Competitor Price Update Result.

Competitor-price update pipeline in a running state
Check the run-start notification and running state.

Success looks like this

  • Output rows: 46,700
  • Rows whose competitor price changes in the current seed: 46,444
  • Rows whose value stays the same: 256
  • Output mode: overwrite
FieldBeforeAfterInterpretation
item_code72240008947224000894Same product
branch_nameGangnam Finance BranchGangnam Finance BranchBranch preserved
inventory_qty5151Inventory preserved
selling_price_krw_synthKRW 4,490KRW 4,490Selling price preserved
competitor_price_krw_synthKRW 4,500KRW 4,670Competitor price enriched

Interpret the result

The pipeline did not append 46,700 new facts. It preserved the original inventory-row structure while enriching the comparison field. overwrite keeps the output as one current snapshot.

Troubleshooting — if the run fails
  1. Verify that both input datasets have more than zero rows.
  2. Verify that price_krw is numeric rather than a string containing a currency symbol.
  3. Verify that the output has a new version and 46,700 rows.

Next decision

Price and inventory are now comparable in one row. Next, expand a product into its branch, region, and supplier relationships to identify the operational context for follow-up.